Triple
T20318141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bechtel Mining & Metals |
E492135
|
entity |
| Predicate | offersServicePhase |
P139642
|
FINISHED |
| Object | concept studies |
—
|
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: concept studies | Statement: [Bechtel Mining & Metals, offersServicePhase, concept studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersServicePhase Context triple: [Bechtel Mining & Metals, offersServicePhase, concept studies]
-
A.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of another entity.
-
B.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
C.
offersLimitedServiceOn
Indicates that one entity provides a restricted, partial, or reduced version of a service to another entity, rather than full or regular service.
-
D.
offersProcedure
Indicates that one entity provides or makes available a specific procedure to another entity.
-
E.
offersServiceOn
Indicates that one entity provides or makes a service available on, during, or through another entity (such as a platform, date, or location).
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67789d8108190ae2e134f4b0b0be5 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:20 a.m.