Triple
T11476620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seleção |
E272038
|
entity |
| Predicate | continentalConfederationFounded |
P79234
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [Seleção, continentalConfederationFounded, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentalConfederationFounded Context triple: [Seleção, continentalConfederationFounded, 1916]
-
A.
confederationFounded
chosen
Indicates that a confederation was established or brought into existence at a particular time or by a particular founding event.
-
B.
confederationFoundedBy
Indicates that a confederation was established or created by a specific person, group, or entity.
-
C.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
D.
regionOfConfederation
Indicates that a given region belongs to, is part of, or is administered within a particular confederation.
-
E.
confederation2
Indicates a formal alliance or union in which multiple entities join together under a shared framework while retaining their individual autonomy.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294e0fe08190b018e840146e27ca |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.