Triple
T33843185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wongar |
E867408
|
entity |
| Predicate | isAlternativeTermFor |
P46176
|
FINISHED |
| Object | Dreaming |
—
|
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: Dreaming | Statement: [Wongar, isAlternativeTermFor, Dreaming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlternativeTermFor Context triple: [Wongar, isAlternativeTermFor, Dreaming]
-
A.
termAlsoUsedFor
chosen
Indicates that one term is also used to refer to the same or closely related concept as another term.
-
B.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
C.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
D.
alternativeAbbreviation
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
E.
notPreferredTermFor
Indicates that one term is a non-preferred or deprecated label that should be replaced by another, preferred term in a controlled vocabulary or terminology system.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700516f688190aa62ea1ee73ddfeb |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.