Triple
T37228325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Army Surplus Special |
E923063
|
entity |
| Predicate | hasCrewMemberRank |
P21967
|
FINISHED |
| Object | Sergeant |
—
|
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: Sergeant | Statement: [The Army Surplus Special, hasCrewMemberRank, Sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrewMemberRank Context triple: [The Army Surplus Special, hasCrewMemberRank, Sergeant]
-
A.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
-
B.
hasCrewRole
chosen
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
C.
hasCrewCharacteristic
Indicates that a crew possesses a specified attribute, quality, or defining feature.
-
D.
hasNotableCrewMember
Indicates that an entity is associated with a crew member who is considered notable or distinguished in some way.
-
E.
missionRoleCrew-1
Indicates that a crew member participates in a mission in a specific operational role or capacity.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:15 p.m.