Triple
T33515776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Danube |
E858360
|
entity |
| Predicate | testAssociation |
P177061
|
FINISHED |
| Object | British nuclear tests in Australia |
—
|
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: British nuclear tests in Australia | Statement: [Blue Danube, testAssociation, British nuclear tests in Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testAssociation Context triple: [Blue Danube, testAssociation, British nuclear tests in Australia]
-
A.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
B.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
-
C.
supportsAssociationWith
Indicates that one entity provides backing, endorsement, or assistance for an association or relationship involving another entity.
-
D.
doctrineAssociation
Indicates an association or connection between entities based on a shared doctrine, belief system, or set of principles.
-
E.
catalogueAssociation
Indicates an association between an entity and a catalogue, such as inclusion, listing, or reference within that catalogue.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:39 a.m.