Triple
T20280678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wardaman people |
E503131
|
entity |
| Predicate | haveConnectionTo |
P8776
|
FINISHED |
| Object | land |
—
|
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: land | Statement: [Wardaman people, haveConnectionTo, land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveConnectionTo Context triple: [Wardaman people, haveConnectionTo, land]
-
A.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
-
B.
hasConnection
chosen
Indicates that there exists a link, association, or relationship between two entities.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
hasConnectionToWork
Indicates that one entity is linked or related to another through a work-related or professional connection.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768e9f0881909c8fe8772dafd468 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:38 a.m.