Triple
T11739916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambert conformal conic projection |
E279124
|
entity |
| Predicate | standardParallelType |
P101097
|
FINISHED |
| Object | one standard parallel |
—
|
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: one standard parallel | Statement: [Lambert conformal conic projection, standardParallelType, one standard parallel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardParallelType Context triple: [Lambert conformal conic projection, standardParallelType, one standard parallel]
-
A.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
D.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
E.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f025f88190a39280806c9d7c33 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.