Triple
T13173662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANZAC Bridge |
E313041
|
entity |
| Predicate | namedInHonourOf |
P8373
|
FINISHED |
| Object | ANZAC soldiers |
—
|
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: ANZAC soldiers | Statement: [ANZAC Bridge, namedInHonourOf, ANZAC soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedInHonourOf Context triple: [ANZAC Bridge, namedInHonourOf, ANZAC soldiers]
-
A.
isGivenInHonorOf
Indicates that something (such as an award, gift, or event) is presented or dedicated as a mark of respect or recognition for a particular person or entity.
-
B.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
C.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
D.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
E.
hasPartInHisHonor
chosen
Indicates that something includes or contains a part, section, or component that is dedicated or named in honor of a particular person.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.