Triple
T11739892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambert azimuthal equal-area projection |
E279123
|
entity |
| Predicate | mapEdgeShape |
P31590
|
FINISHED |
| Object | circle when centered on a point |
—
|
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: circle when centered on a point | Statement: [Lambert azimuthal equal-area projection, mapEdgeShape, circle when centered on a point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapEdgeShape Context triple: [Lambert azimuthal equal-area projection, mapEdgeShape, circle when centered on a point]
-
A.
formsEdgeOf
chosen
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
B.
trackShape
Indicates the geometric form or layout pattern that a track follows.
-
C.
routeSymbolShape
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
-
D.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
E.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
- 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_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. |
Created at: April 8, 2026, 9:41 p.m.