Triple
T34815024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Archer / Castor Troy in Face/Off |
E1003607
|
entity |
| Predicate | hasComponentIdentity |
P40349
|
FINISHED |
| Object | Sean Archer |
E1006446
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Sean Archer | Statement: [Sean Archer / Castor Troy in Face/Off, hasComponentIdentity, Sean Archer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentIdentity Context triple: [Sean Archer / Castor Troy in Face/Off, hasComponentIdentity, Sean Archer]
-
A.
hasIdentityComponent
chosen
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
B.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
C.
hasDistinctIdentity
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
-
D.
hasMemberWithIdentity
Indicates that a group or collection includes at least one member that possesses a specified identity or identifier.
-
E.
hasIdentityStatus
Indicates that an entity is associated with a particular identity-related state or condition (such as confirmed, provisional, or unknown).
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fb5819c8190999fac08e77483de |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.