Triple
T900980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Lieutenant |
E19444
|
entity |
| Predicate | isInMilitaryBranch |
P253
|
FINISHED |
| Object | army |
—
|
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: army | Statement: [Second Lieutenant, isInMilitaryBranch, army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInMilitaryBranch Context triple: [Second Lieutenant, isInMilitaryBranch, army]
-
A.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
C.
hasMilitaryDivision
Indicates that an entity possesses, includes, or is organizationally associated with a specific military division.
-
D.
militaryBranchEmphasis
Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
-
E.
hasMilitaryServiceStart
Indicates the date or point in time when an entity’s period of military service began.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad42ecac81909f8bc554d2fe0363 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.