Triple
T32374854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphurus |
E827249
|
entity |
| Predicate | livesOnOrNear |
P41003
|
FINISHED |
| Object | sea floor |
—
|
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: sea floor | Statement: [Symphurus, livesOnOrNear, sea floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesOnOrNear Context triple: [Symphurus, livesOnOrNear, sea floor]
-
A.
residesNear
chosen
Indicates that one entity lives or is located in close physical proximity to another entity.
-
B.
livesOn
Indicates that one entity resides or has its home on or atop another entity (such as a surface, structure, or geographic feature).
-
C.
oftenLocatedNear
Indicates that one entity is frequently found in close physical proximity to another entity.
-
D.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
E.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:50 a.m.