Triple
T28541065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Around the Horn |
E722290
|
entity |
| Predicate | hasFinalSegment |
P193300
|
FINISHED |
| Object | Face Time |
—
|
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: Face Time | Statement: [Around the Horn, hasFinalSegment, Face Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalSegment Context triple: [Around the Horn, hasFinalSegment, Face Time]
-
A.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
B.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
C.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
D.
hasSegmentOver
Indicates that one segment spatially extends above or across another segment.
-
E.
isHeadFinal
Indicates that in a given linguistic structure, the head of a phrase follows (comes after) its dependents or modifiers.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 28, 2026, 3:35 a.m.