Triple
T8161567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poplars, Spring |
E190586
|
entity |
| Predicate | hasSeriesSubject |
P81031
|
FINISHED |
| Object | poplar trees along a river |
—
|
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: poplar trees along a river | Statement: [Poplars, Spring, hasSeriesSubject, poplar trees along a river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesSubject Context triple: [Poplars, Spring, hasSeriesSubject, poplar trees along a river]
-
A.
hasPublicationSeries
Indicates that an entity is part of, or associated with, a particular publication series.
-
B.
hasProminentSeries
Indicates that an entity is notably associated with a major or well-known series as a defining feature.
-
C.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
D.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
E.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455559188190bf95d9d93bb76002 |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb40a017608190b6b48cf60335fa8d |
completed | March 31, 2026, 3:33 a.m. |
Created at: March 30, 2026, 5:38 p.m.