Triple
T1077011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAC-1 |
E23861
|
entity |
| Predicate | hasEngagementMode |
P12713
|
FINISHED |
| Object | semi-automatic engagement control |
—
|
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: semi-automatic engagement control | Statement: [PAC-1, hasEngagementMode, semi-automatic engagement control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngagementMode Context triple: [PAC-1, hasEngagementMode, semi-automatic engagement control]
-
A.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
B.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasWorkingMode
chosen
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
E.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b940d4848190930e73597afd1fcf |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.