Triple
T30098525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infant Lancelot |
E764931
|
entity |
| Predicate | futureIdentity |
P168447
|
FINISHED |
| Object | Sir Lancelot |
—
|
NE NERFINISHED |
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: Sir Lancelot | Statement: [Infant Lancelot, futureIdentity, Sir Lancelot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureIdentity Context triple: [Infant Lancelot, futureIdentity, Sir Lancelot]
-
A.
globalIdentity
Indicates that two or more identifiers or representations actually refer to the same underlying global entity or individual.
-
B.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
C.
adoptedIdentity
Indicates that one entity has taken on or assumed the identity, role, or persona of another entity, either formally or informally.
-
D.
identityShapedBy
Indicates that one entity’s identity is influenced, formed, or defined by another entity or factor.
-
E.
planningIdentity
Indicates that an entity serves as the specific identity or role under which planning or plan-related activities are carried out.
- F. None of above. chosen
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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d92dbdc8190ae3e8f67b979cb5c |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:08 p.m.