Triple
T23713812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Alta |
E585940
|
entity |
| Predicate | isSpokenInPartOf |
P141433
|
FINISHED |
| Object | northern Aurora province |
—
|
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: northern Aurora province | Statement: [Northern Alta, isSpokenInPartOf, northern Aurora province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenInPartOf Context triple: [Northern Alta, isSpokenInPartOf, northern Aurora province]
-
A.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
B.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
C.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
D.
isSpokenInAdministrativeUnit
chosen
Indicates that a particular language is used or officially spoken within a specified administrative unit or region.
-
E.
isHeardIn
Indicates that a sound, voice, or audio from one entity is perceived or audible within the context, location, or medium of another entity.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b7793e3c8190960462a9f928d269 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.