Triple
T33124829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boarding House |
E847692
|
entity |
| Predicate | placeInCollectionOrder |
P82023
|
FINISHED |
| Object | seventh story in Dubliners |
—
|
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: seventh story in Dubliners | Statement: [The Boarding House, placeInCollectionOrder, seventh story in Dubliners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInCollectionOrder Context triple: [The Boarding House, placeInCollectionOrder, seventh story in Dubliners]
-
A.
placedInOrderBy
Indicates that one entity was arranged or positioned according to a sequence or priority determined by another entity.
-
B.
collectionPosition
chosen
Indicates the relative ordering or placement of an item within a collection or sequence.
-
C.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
D.
previouslyPlacedInOrder
Indicates that an item or entity has already been included in a prior order before the current context or transaction.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:27 a.m.