Triple
T12984556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercator projection |
E321733
|
entity |
| Predicate | scaleFactor |
P58733
|
FINISHED |
| Object | true at the equator |
—
|
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: true at the equator | Statement: [Mercator projection, scaleFactor, true at the equator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleFactor Context triple: [Mercator projection, scaleFactor, true at the equator]
-
A.
scaleProperty
Indicates that one entity defines or modifies the scale, magnitude, or proportional sizing used to interpret or represent a property of another entity.
-
B.
scalingProperty
chosen
Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
-
C.
scaleDefinition
Indicates that an entity specifies the parameters, structure, or measurement system used to define a particular scale.
-
D.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
E.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:40 p.m.