Triple
T31076348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Anzac (fictional cruiser) |
E791974
|
entity |
| Predicate | settingLocationContext |
P181347
|
FINISHED |
| Object | Australian naval forces based in Melbourne |
—
|
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: Australian naval forces based in Melbourne | Statement: [HMAS Anzac (fictional cruiser), settingLocationContext, Australian naval forces based in Melbourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingLocationContext Context triple: [HMAS Anzac (fictional cruiser), settingLocationContext, Australian naval forces based in Melbourne]
-
A.
setLocation
Indicates assigning or updating the place or position where an entity is located.
-
B.
settingLocationType
Indicates the type or category of location in which an event, action, or situation takes place.
-
C.
controlsLocation
Indicates that one entity has authority over, manages, or determines the status or use of a particular location.
-
D.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 9:02 p.m.