Triple
T27519246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | organizedByState |
P171427
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East German football league system, organizedByState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedByState Context triple: [East German football league system, organizedByState, true]
-
A.
organizedInState
Indicates that an organization or entity is legally formed, registered, or established within a particular state.
-
B.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
C.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
D.
areOrganizedBy
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
-
E.
organizerJurisdiction
Indicates the jurisdiction or authority under which an organizer operates or is legally registered.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 1:20 p.m.