Triple
T22706830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austria national football team |
E561477
|
entity |
| Predicate | notableEraPeriod |
P561
|
FINISHED |
| Object | early 1930s |
—
|
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: early 1930s | Statement: [Austria national football team, notableEraPeriod, early 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEraPeriod Context triple: [Austria national football team, notableEraPeriod, early 1930s]
-
A.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
C.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
D.
notableLabelEra
Indicates the historical era or time period for which a label, title, or designation is considered notable or especially relevant.
-
E.
associatedWithNotableEra
Indicates that something has a significant connection or relevance to a historically or culturally notable period of time.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cff7588190a40c8cef0f3cd44a |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:17 p.m.