Triple
T10951319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LORAN |
E258732
|
entity |
| Predicate | positionFixMethod |
P96802
|
FINISHED |
| Object | intersection of hyperbolic lines |
—
|
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: intersection of hyperbolic lines | Statement: [LORAN, positionFixMethod, intersection of hyperbolic lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionFixMethod Context triple: [LORAN, positionFixMethod, intersection of hyperbolic lines]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
C.
positionHead
Indicates that one entity serves as the head or primary governing element in the positional or syntactic structure of another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fc156c8190826e124c13ce7242 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.