Triple
T31704490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAAM |
E809142
|
entity |
| Predicate | engagementRangeCategory |
P61967
|
FINISHED |
| Object | short range |
—
|
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: short range | Statement: [SAAM, engagementRangeCategory, short range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementRangeCategory Context triple: [SAAM, engagementRangeCategory, short range]
-
A.
engagementRange
chosen
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
B.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
C.
engagementScale
Indicates the degree or intensity of involvement, interest, or participation in an activity, interaction, or relationship.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:13 p.m.