Triple
T7478657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traveler |
E176692
|
entity |
| Predicate | hasMultipleIncarnations |
P76487
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Traveler, hasMultipleIncarnations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleIncarnations Context triple: [Traveler, hasMultipleIncarnations, true]
-
A.
hasIncarnationsOfGender
Indicates that an entity has different incarnations or forms that each express or are associated with a particular gender.
-
B.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
C.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
D.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
-
E.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4f13f548190a8cc59165735b30e |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:42 p.m.