Triple
T27343333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | mainEnginesInstalled |
P162547
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Enterprise (OV-101), mainEnginesInstalled, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEnginesInstalled Context triple: [Enterprise (OV-101), mainEnginesInstalled, false]
-
A.
engineName
Indicates the specific name assigned to an engine associated with an entity.
-
B.
numberOfEngines
Indicates the quantity of engines associated with or used by an entity.
-
C.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
D.
historicallySuppliedEnginesFor
Indicates that one entity has, in the past, provided engines to another entity, typically as a supplier or manufacturer.
-
E.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9f5514819088c3a1e11c65a9af |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 11:44 a.m.