Triple
T27734215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CollectionBase |
E697493
|
entity |
| Predicate | isConsideredLegacy |
P167786
|
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: [CollectionBase, isConsideredLegacy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsideredLegacy Context triple: [CollectionBase, isConsideredLegacy, true]
-
A.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
B.
hasLegacyAt
Indicates that an entity has left a lasting impact, influence, or heritage associated with a particular place or context.
-
C.
usesLegacyOf
Indicates that one entity makes use of, builds upon, or derives benefit from the historical work, reputation, or established influence of another entity.
-
D.
hasPartInLegacy
Indicates that an entity includes another entity as a component or constituent specifically within its legacy or historically inherited structure.
-
E.
isLegacyCharacterFor
Indicates that one entity is an older, previously established character associated with or originating from the context, storyline, or franchise of another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 3:12 p.m.