Triple
T1241323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guaraní |
E26662
|
entity |
| Predicate | isKeyElementOf |
P14613
|
FINISHED |
| Object | Paraguayan national identity |
—
|
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: Paraguayan national identity | Statement: [Guaraní, isKeyElementOf, Paraguayan national identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyElementOf Context triple: [Guaraní, isKeyElementOf, Paraguayan national identity]
-
A.
hasKeyElement
chosen
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
C.
isKeyNodeIn
Indicates that a node serves as a primary or critical element within a specified structure, system, or context.
-
D.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
E.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf44ac3c8190a28a333b320305fd |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.