Triple
T3468420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devils Marbles |
E73192
|
entity |
| Predicate | isCoManagedWith |
P13336
|
FINISHED |
| Object | traditional owners |
—
|
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: traditional owners | Statement: [Devils Marbles, isCoManagedWith, traditional owners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoManagedWith Context triple: [Devils Marbles, isCoManagedWith, traditional owners]
-
A.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
B.
coManagedWith
chosen
Indicates that two or more entities share joint responsibility or authority in managing the same resource, project, or process.
-
C.
usesManagementTool
Indicates that one entity employs or operates a management tool to perform or support its management-related activities.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
typeOfLicensingItManaged
Indicates that one entity manages or oversees the licensing arrangements or permissions associated with 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb11ec5881908347bf92883a25ee |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.