Triple
T32972806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XP-72 prototype fighter |
E843570
|
entity |
| Predicate | programScale |
P180367
|
FINISHED |
| Object | limited to prototype evaluation |
—
|
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: limited to prototype evaluation | Statement: [XP-72 prototype fighter, programScale, limited to prototype evaluation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programScale Context triple: [XP-72 prototype fighter, programScale, limited to prototype evaluation]
-
A.
programLevel
Indicates the hierarchical or categorical level at which a program is defined or operates (e.g., undergraduate, graduate, or other tiers).
-
B.
programPace
Indicates the speed or rate at which a program, course, or sequence of activities progresses over time.
-
C.
programLength
Indicates the duration or total length of a program, typically measured in time or size.
-
D.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
E.
programDesignation
Indicates that an entity is assigned or identified by a specific program designation or label.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:22 a.m.