Triple
T38426606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDS |
E903375
|
entity |
| Predicate | precededByFormat |
P196735
|
FINISHED |
| Object | no permanent division series before 1995 |
—
|
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: no permanent division series before 1995 | Statement: [LDS, precededByFormat, no permanent division series before 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByFormat Context triple: [LDS, precededByFormat, no permanent division series before 1995]
-
A.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
B.
precededByInGroup
Indicates that one entity comes before another in the ordered sequence within the same group or collection.
-
C.
precededBySegment
Indicates that one segment occurs immediately before another segment in a sequence or ordering.
-
D.
precededByInBand
Indicates that one element occurs earlier than another within the ordered sequence of items in the same band or grouping.
-
E.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.