Triple
T33425387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | congresos de la CONMEBOL |
E855960
|
entity |
| Predicate | seRigenPor |
P141473
|
FINISHED |
| Object | estatutos de la CONMEBOL |
—
|
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: estatutos de la CONMEBOL | Statement: [congresos de la CONMEBOL, seRigenPor, estatutos de la CONMEBOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seRigenPor Context triple: [congresos de la CONMEBOL, seRigenPor, estatutos de la CONMEBOL]
-
A.
seRigePor
chosen
Indicates that one entity is governed, regulated, or guided by the rules, principles, or criteria established by another entity or system.
-
B.
eraSequence
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
C.
seiMeans
Indicates that one entity serves as the meaning, definition, or semantic content of another entity.
-
D.
Juyo
Indicates a relationship where one entity is associated with or characterized by the concept or style referred to as "Juyo."
-
E.
seos
Indicates a search engine optimization (SEO) relationship, where one entity improves or influences the visibility, ranking, or discoverability of another in search results.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.