Triple
T16960838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa América 1953 matches |
E411421
|
entity |
| Predicate | federationScope |
P66265
|
FINISHED |
| Object | continental |
—
|
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: continental | Statement: [Copa América 1953 matches, federationScope, continental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federationScope Context triple: [Copa América 1953 matches, federationScope, continental]
-
A.
confederationScope
chosen
Indicates the extent or domain within which a confederation’s authority, agreements, or cooperative arrangements apply.
-
B.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
C.
allianceScope
Indicates the extent or boundaries of cooperation and mutual obligations defined within an alliance relationship.
-
D.
federation
Indicates that an entity is formally associated with, governed by, or part of a larger federated organization or system.
-
E.
federatedOn
Indicates that an entity participates in or is governed through a federated structure, system, or framework based on 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.