Triple
T27893356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asturias autonomous football team |
E705417
|
entity |
| Predicate | representsPeopleFrom |
P33418
|
FINISHED |
| Object | Asturian players |
—
|
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: Asturian players | Statement: [Asturias autonomous football team, representsPeopleFrom, Asturian players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsPeopleFrom Context triple: [Asturias autonomous football team, representsPeopleFrom, Asturian players]
-
A.
representsPeople
chosen
Indicates that one entity serves as a representation or stand-in for one or more people.
-
B.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
includedRepresentativesFrom
Indicates that one entity’s composition or delegation contained representatives originating from another specified entity.
-
D.
representedFrom
Indicates that one entity serves as a representation or depiction of another entity.
-
E.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 6:37 p.m.