Triple
T26094450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindmarsh Island Bridge |
E658220
|
entity |
| Predicate | controversyPeriod |
P28865
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Hindmarsh Island Bridge, controversyPeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controversyPeriod Context triple: [Hindmarsh Island Bridge, controversyPeriod, 1990s]
-
A.
controversialAtTimeOfPublication
Indicates that something was the subject of significant disagreement, debate, or public dispute at the time it was originally published.
-
B.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
C.
controversyType
Indicates the specific kind or category of controversy associated with an entity or situation.
-
D.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
E.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 7:50 p.m.