Triple
T13682652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger Assessment and Selection Program |
E328039
|
entity |
| Predicate | isIntensive |
P107620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ranger Assessment and Selection Program, isIntensive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntensive Context triple: [Ranger Assessment and Selection Program, isIntensive, true]
-
A.
isIntense
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
B.
extensiveOrIntensive
chosen
Indicates whether a property or quantity is characterized as extensive (dependent on system size or amount) or intensive (independent of system size or amount) in the relationship being described.
-
C.
isExpensive
Indicates that something has a high cost or price relative to typical or expected alternatives.
-
D.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
E.
hasCentralIntensity
Indicates that something possesses a specific value or measure of intensity at its central point or core region.
- F. None of above.
Provenance (3 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.