Triple
T7910080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Selfridge |
E183673
|
entity |
| Predicate | overseesExtractionOf |
P79724
|
FINISHED |
| Object | unobtanium |
—
|
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: unobtanium | Statement: [Parker Selfridge, overseesExtractionOf, unobtanium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesExtractionOf Context triple: [Parker Selfridge, overseesExtractionOf, unobtanium]
-
A.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
B.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
C.
overseesParticipationOf
Indicates that one entity supervises, manages, or has authority over another entity’s involvement in an activity, process, or group.
-
D.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
E.
beamExtractionMethod
Indicates the method or technique used to extract or generate a beam from a source.
- F. None of above. chosen
Provenance (4 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5db9508190bbe92673ef5a7861 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:04 p.m.