Triple
T27343327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | approachAndLandingTestsEnd |
P185626
|
FINISHED |
| Object | 1977-10 |
—
|
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: 1977-10 | Statement: [Enterprise (OV-101), approachAndLandingTestsEnd, 1977-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachAndLandingTestsEnd Context triple: [Enterprise (OV-101), approachAndLandingTestsEnd, 1977-10]
-
A.
approachAndLandingTestsStart
Indicates the point in time when approach and landing test activities begin.
-
B.
approachAndLandingTestsLocation
Indicates the location where approach and landing tests are conducted.
-
C.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
D.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
E.
precisionLandingDemonstration
Indicates a controlled landing event where an object or vehicle is guided to touch down at a highly specific, predefined location to demonstrate landing accuracy.
- 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_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 27, 2026, 11:44 a.m.