Triple
T13767363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Sociedad |
E330783
|
entity |
| Predicate | hasFutsalSection |
P110876
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Real Sociedad, hasFutsalSection, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFutsalSection Context triple: [Real Sociedad, hasFutsalSection, no]
-
A.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
-
B.
hasBallcourt
Indicates that a place, structure, or site includes or is equipped with a ballcourt as one of its features.
-
C.
hasFootballArrangementWith
Indicates a formal or informal agreement or setup between entities specifically related to playing, organizing, or managing football activities or events.
-
D.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
E.
hasFootballSubdivision
Indicates that an organization or institution includes a specific football-related division or sub-unit within its structure.
- F. None of above. chosen
Provenance (4 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0227f2c48190983ccc9395e4e7a2 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:10 p.m.