Triple
T20003655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WKInterfaceMap |
E494395
|
entity |
| Predicate | usesMapRectType |
P138312
|
FINISHED |
| Object | MKMapRect |
—
|
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: MKMapRect | Statement: [WKInterfaceMap, usesMapRectType, MKMapRect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMapRectType Context triple: [WKInterfaceMap, usesMapRectType, MKMapRect]
-
A.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
B.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
C.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
D.
isRegularMap
Indicates that a mapping between two mathematical structures preserves the required regularity conditions (such as continuity, differentiability, or algebraic regularity) specified for that context.
-
E.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:33 p.m.