Triple
T24416924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Wien |
E615608
|
entity |
| Predicate | memberOfAssociation |
P10
|
FINISHED |
| Object | Austrian Football Association |
—
|
NE NERFINISHED |
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: Austrian Football Association | Statement: [Rapid Wien, memberOfAssociation, Austrian Football Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfAssociation Context triple: [Rapid Wien, memberOfAssociation, Austrian Football Association]
-
A.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
B.
memberOf
chosen
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
C.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
D.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
E.
endedAssociationWith
Indicates that a previously existing association or relationship between two entities has been terminated or discontinued.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958645248190a22bd0b8bcc2dfe2 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.