Triple
T24360086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eora |
E614031
|
entity |
| Predicate | originalCustodiansOf |
P114319
|
FINISHED |
| Object | Sydney Harbour |
—
|
NE NERFINISHED |
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 | Statement: [Eora, originalCustodiansOf, Sydney Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCustodiansOf Context triple: [Eora, originalCustodiansOf, Sydney Harbour]
-
A.
traditionalCustodianOf
chosen
Indicates that an entity holds recognized traditional responsibility, authority, or guardianship over another entity, often in a cultural, ancestral, or customary context.
-
B.
firstHoldersBelongedTo
Indicates that the initial holders or owners of something were members of, or affiliated with, a particular group, organization, or category.
-
C.
originalHolder
Indicates that an entity is the initial possessor or owner of another entity before any transfer, change, or reassignment occurs.
-
D.
probableOriginalOwner
Indicates that one entity is likely, though not certainly, the original owner or possessor of another entity.
-
E.
originalSignatory
Indicates that an entity was an initial party that formally signed or agreed to a document, contract, or treaty at the time it was first executed.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29383ccb88190a4752fe7ccd93fd5 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.