Triple
T38226579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialist |
E1012160
|
entity |
| Predicate | hasLeadershipTrackEquivalent |
P14530
|
FINISHED |
| Object | Corporal |
—
|
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: Corporal | Statement: [Specialist, hasLeadershipTrackEquivalent, Corporal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadershipTrackEquivalent Context triple: [Specialist, hasLeadershipTrackEquivalent, Corporal]
-
A.
hasLeadershipFunction
Indicates that an entity holds or performs a leadership role, responsibility, or function in relation to another entity or context.
-
B.
hasTypeOfLeadership
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
-
C.
hasLeadershipRoleSince
Indicates that an entity has held a leadership role starting from a specified point in time and continuing from that date onward.
-
D.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
E.
hasCareerTrack
chosen
Indicates that an entity is associated with or follows a particular career path or professional progression.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:30 p.m.