Triple
T6737879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LS |
E154001
|
entity |
| Predicate | successorTrimInHierarchy |
P72665
|
FINISHED |
| Object | LT |
—
|
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: LT | Statement: [LS, successorTrimInHierarchy, LT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTrimInHierarchy Context triple: [LS, successorTrimInHierarchy, LT]
-
A.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
B.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
-
C.
successorChild
Indicates that one entity is the child of another entity who is its immediate predecessor or predecessor in a succession or lineage.
-
D.
successorPrefix
Indicates that one sequence is formed by taking another sequence and replacing its final element with its immediate successor, while keeping all preceding elements identical.
-
E.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1850a288190aa7e647fefbb0ede |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.