Triple
T269720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Entrance Processing Station |
E5603
|
entity |
| Predicate | stageOf |
P9657
|
FINISHED |
| Object | military accession process |
—
|
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: military accession process | Statement: [Military Entrance Processing Station, stageOf, military accession process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageOf Context triple: [Military Entrance Processing Station, stageOf, military accession process]
-
A.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
B.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
C.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
-
D.
competitionStage
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
E.
isStageInCareerOf
Indicates that one entity represents a particular phase or stage within the professional career of another entity.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db00ed48190be6f598807265356 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d6ec9688190b2ba027756b57d25 |
completed | Feb. 28, 2026, 3:13 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.