Triple
T36733298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finance Corps |
E907396
|
entity |
| Predicate | hasEnlistedPersonnel |
P195477
|
FINISHED |
| Object | finance specialists |
—
|
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: finance specialists | Statement: [Finance Corps, hasEnlistedPersonnel, finance specialists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnlistedPersonnel Context triple: [Finance Corps, hasEnlistedPersonnel, finance specialists]
-
A.
hasVolunteerPersonnelFrom
Indicates that an entity receives or utilizes volunteer personnel supplied by another entity or source.
-
B.
hasEmbarkedPersonnel
Indicates that one entity has taken personnel on board or loaded them for transport or deployment.
-
C.
hasEnlistedRank
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical organization.
-
D.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
-
E.
hasGeneralStaff
Indicates that an entity has, is associated with, or is served by a general staff body responsible for overall strategic or administrative functions.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4:12 p.m.