Triple
T23225193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFCAT |
E580994
|
entity |
| Predicate | hasNegativeMarking |
P65563
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AFCAT, hasNegativeMarking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNegativeMarking Context triple: [AFCAT, hasNegativeMarking, yes]
-
A.
negativeMarking
chosen
Indicates that an entity assigns or receives a penalty, deduction, or unfavorable score in response to a particular action, performance, or condition.
-
B.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
C.
wasMarkedBy
Indicates that an entity bears a mark, sign, or indication that was applied or caused by another entity.
-
D.
hasProofMark
Indicates that an entity bears a specific proof mark signifying it has passed an official test or inspection.
-
E.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922d30b08190a3c54bab58f5c8e7 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.