Triple
T35575295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smart #1 |
E1028057
|
entity |
| Predicate | successorToConcept |
P43210
|
FINISHED |
| Object | Smart Concept #1 |
—
|
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: Smart Concept #1 | Statement: [Smart #1, successorToConcept, Smart Concept #1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorToConcept Context triple: [Smart #1, successorToConcept, Smart Concept #1]
-
A.
successorConcept
chosen
Indicates that one concept directly follows and replaces another in a sequence, versioning, or conceptual progression.
-
B.
successorInIdea
Indicates that one idea conceptually follows, develops from, or replaces another in a sequence of intellectual progression.
-
C.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
-
D.
predecessorInConcept
Indicates that one concept temporally or logically comes before another in a sequence or developmental progression.
-
E.
successorInTheory
Indicates that one entity directly follows and replaces another within a specified theoretical framework or system.
- F. None of above.
Provenance (3 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:04 p.m.