Triple
T16307134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hampshire–Massachusetts border |
E395948
|
entity |
| Predicate | hasCoordinateBasis |
P122623
|
FINISHED |
| Object | line of latitude near 42 degrees north |
—
|
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: line of latitude near 42 degrees north | Statement: [New Hampshire–Massachusetts border, hasCoordinateBasis, line of latitude near 42 degrees north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinateBasis Context triple: [New Hampshire–Massachusetts border, hasCoordinateBasis, line of latitude near 42 degrees north]
-
A.
hasStandardBasis
Indicates that a given vector space is equipped with or possesses its usual canonical set of basis vectors.
-
B.
isCoordinateFree
Indicates that a property, formulation, or expression does not depend on any particular choice of coordinate system.
-
C.
hasCanonicalBasis
Indicates that there exists a standard or preferred basis associated with an entity, typically used as the reference basis in its context.
-
D.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
E.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d63b688190ad5ebc3fb5dd5b4c |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.