Triple
T8596595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 112 |
E203563
|
entity |
| Predicate | statusInCompetition |
P83772
|
FINISHED |
| Object | unsuccessful |
—
|
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: unsuccessful | Statement: [Heinkel He 112, statusInCompetition, unsuccessful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInCompetition Context triple: [Heinkel He 112, statusInCompetition, unsuccessful]
-
A.
competitionStatus
Indicates the current state or phase of a competition, such as whether it is upcoming, ongoing, paused, or completed.
-
B.
positionOnCompetition
Indicates the ranking or place an entity holds within the results of a specific competition.
-
C.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
D.
competitiveStatus
Indicates the nature or level of competition that exists between entities, such as whether they are rivals, collaborators, or non-competitors.
-
E.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c945dc8190a313c61c0db46187 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:23 p.m.