Triple
T28482359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Market |
E720726
|
entity |
| Predicate | predecessorSegments |
P152543
|
FINISHED |
| Object | First Section |
—
|
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: First Section | Statement: [Prime Market, predecessorSegments, First Section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorSegments Context triple: [Prime Market, predecessorSegments, First Section]
-
A.
predecessorCollectionOf
Indicates that one collection temporally or sequentially comes before and leads into another collection.
-
B.
predecessorSeries
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
C.
precededBySegment
chosen
Indicates that one segment occurs immediately before another segment in a sequence or ordering.
-
D.
predecessorGroup
Indicates that one group existed or held a role before and was replaced or succeeded by another group in a sequence or lineage.
-
E.
predecessorUsedFrom
Indicates that something was used or derived from a preceding version, state, or entity that came before it.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 2:56 a.m.