Triple
T18075611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pararescuemen |
E432544
|
entity |
| Predicate | pipelineLength |
P129716
|
FINISHED |
| Object | approximately two years |
—
|
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: approximately two years | Statement: [Pararescuemen, pipelineLength, approximately two years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipelineLength Context triple: [Pararescuemen, pipelineLength, approximately two years]
-
A.
pipelineDepth
Indicates the number of sequential processing stages or steps that data or tasks pass through in a pipeline.
-
B.
laneLength
Indicates the length or distance of a lane in a given context.
-
C.
pipeline
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
-
D.
circuitLength
Indicates the total measured length or distance of a circuit or closed path.
-
E.
channelLength
Indicates the measured extent or distance from one end of a channel to the other.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9f4f76c81909015ae4d66d1c85f |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.