Triple
T35512548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moruya, New South Wales |
E1026321
|
entity |
| Predicate | graniteUsedFor |
P71689
|
FINISHED |
| Object | Sydney Harbour Bridge pylons |
—
|
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: Sydney Harbour Bridge pylons | Statement: [Moruya, New South Wales, graniteUsedFor, Sydney Harbour Bridge pylons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graniteUsedFor Context triple: [Moruya, New South Wales, graniteUsedFor, Sydney Harbour Bridge pylons]
-
A.
marbleUsedFor
Indicates that one entity (a marble) is employed or utilized for a particular purpose, function, or application in relation to another entity.
-
B.
materialFromQuarriesUsedFor
chosen
Indicates that material extracted from quarries is used for a particular purpose, project, or object.
-
C.
brickTypeUsedFor
Indicates that a particular type of brick is used for constructing or forming a specified object, structure, or component.
-
D.
stoneMaterial
Indicates that something is made of, or primarily composed of, stone as its material.
-
E.
marbleType
Indicates that one entity is of a specific type or category of marble in relation 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.