Triple
T37593592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azsuna |
E935320
|
entity |
| Predicate | continentMapID |
P195523
|
FINISHED |
| Object | 122 |
—
|
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: 122 | Statement: [Azsuna, continentMapID, 122]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentMapID Context triple: [Azsuna, continentMapID, 122]
-
A.
continentReference
Indicates that one entity serves as a reference or pointer to a specific continent associated with another entity.
-
B.
continentLocationSymbolized
Indicates that one entity symbolically represents or denotes the continental location of another entity.
-
C.
continentDistribution
Indicates how something is geographically distributed or spread across different continents.
-
D.
continentConfiguration
Indicates how landmasses and oceans are spatially arranged and distributed on a planet’s surface at a given time.
-
E.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:18 p.m.