Triple
T27964722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radomiro Tomic mine |
E704684
|
entity |
| Predicate | isStateOwnedOperation |
P16269
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Radomiro Tomic mine, isStateOwnedOperation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStateOwnedOperation Context triple: [Radomiro Tomic mine, isStateOwnedOperation, true]
-
A.
isStateOwned
chosen
Indicates that an entity is owned or controlled by a government or state authority.
-
B.
hasOwnerOperator
Indicates that an entity is owned and operated by a specified party, combining both ownership and operational responsibility in a single relationship.
-
C.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
D.
ownerOfAssociatedOperation
Indicates that one entity is the owner or controlling party of an operation that is functionally or contextually associated with another entity.
-
E.
hasLockOperation
Indicates that an entity is associated with a specific lock-related operation, such as locking, unlocking, or otherwise controlling access.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 7:34 p.m.