Triple
T12010182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Tongue (Westeros) |
E285884
|
entity |
| Predicate | statusInWesteros |
P33417
|
FINISHED |
| Object | lingua franca |
—
|
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: lingua franca | Statement: [Common Tongue (Westeros), statusInWesteros, lingua franca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInWesteros Context triple: [Common Tongue (Westeros), statusInWesteros, lingua franca]
-
A.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
B.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
C.
statusInRegion
chosen
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
D.
legalStatusInEmpire
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d61a4c81909e6cb6500b61df94 |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.