Triple
T33924645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Constellation (testbed) |
E869714
|
entity |
| Predicate | primaryTestRole |
P206738
|
FINISHED |
| Object | jet engine testbed |
—
|
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: jet engine testbed | Statement: [Lockheed Constellation (testbed), primaryTestRole, jet engine testbed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTestRole Context triple: [Lockheed Constellation (testbed), primaryTestRole, jet engine testbed]
-
A.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
B.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
C.
principalRoleIn
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
D.
primaryAdministrativeRole
Indicates that an entity holds the main or most significant administrative position or function in relation to another entity.
-
E.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.