Triple
T25132872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schneider family |
E629572
|
entity |
| Predicate | ownedAssets |
P26628
|
FINISHED |
| Object | mines |
—
|
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: mines | Statement: [Schneider family, ownedAssets, mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedAssets Context triple: [Schneider family, ownedAssets, mines]
-
A.
eligibleAssets
Indicates that certain assets meet the required criteria or conditions to qualify for a specified purpose or treatment.
-
B.
ownsAssetType
chosen
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465fb5eb88190bb30b07f57fe4e8d |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:28 a.m.