Triple
T27519266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | hadClubReorganizations |
P162473
|
FINISHED |
| Object | frequent |
—
|
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: frequent | Statement: [East German football league system, hadClubReorganizations, frequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadClubReorganizations Context triple: [East German football league system, hadClubReorganizations, frequent]
-
A.
isPartOfReorganization
Indicates that an entity is involved in, or belongs to, a structural or organizational reconfiguration process.
-
B.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
C.
typeOfReorganization
Indicates the specific kind or category of organizational restructuring that is being or has been carried out.
-
D.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
E.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
- 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_69f62f2accf081908b50f8473deda2de |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:20 p.m.