Triple
T32516532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7748 |
E831074
|
entity |
| Predicate | definesCoordinateSystem |
P191634
|
FINISHED |
| Object | Montgomery x-coordinate |
—
|
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: Montgomery x-coordinate | Statement: [RFC 7748, definesCoordinateSystem, Montgomery x-coordinate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCoordinateSystem Context triple: [RFC 7748, definesCoordinateSystem, Montgomery x-coordinate]
-
A.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
B.
coordinateSystemFor
chosen
Indicates that one entity serves as the coordinate system or reference frame used to define the position, orientation, or measurement of another entity.
-
C.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
D.
coordinateSystemBehavior
Indicates how positions, orientations, or transformations are defined, interpreted, and updated within a particular coordinate system.
-
E.
formsCoordinateCollegeSystemWith
Indicates that two educational institutions jointly participate in and operate as parts of a shared, coordinated college system.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 1, 2026, 1 a.m.