Triple
T35407010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Services Schedule |
E1023384
|
entity |
| Predicate | contractVehicleFor |
P198246
|
FINISHED |
| Object | long-term professional services requirements |
—
|
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: long-term professional services requirements | Statement: [Professional Services Schedule, contractVehicleFor, long-term professional services requirements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractVehicleFor Context triple: [Professional Services Schedule, contractVehicleFor, long-term professional services requirements]
-
A.
vehicleFor
Indicates that one entity serves as the means of transportation or conveyance for another entity.
-
B.
intendedForVehicle
Indicates that something is designed, meant, or suitable to be used with or by a particular vehicle.
-
C.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
D.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
-
E.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
| PDg | Predicate description generation | batch_69fed48c92ec8190b3be88880d86de86 |
completed | May 9, 2026, 6:30 a.m. |
Created at: May 3, 2026, 4:03 p.m.