Triple
T32185842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaman (United States Navy) |
E822105
|
entity |
| Predicate | advancementDependsOn |
P173830
|
FINISHED |
| Object | time in service |
—
|
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: time in service | Statement: [Seaman (United States Navy), advancementDependsOn, time in service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancementDependsOn Context triple: [Seaman (United States Navy), advancementDependsOn, time in service]
-
A.
statusDependsOn
Indicates that the status or state of one entity is determined or influenced by the status or state of another entity.
-
B.
advancementControl
Indicates a relationship where one entity directs, manages, or regulates the progress or forward movement of another entity or process.
-
C.
advancementStatus
Indicates the current stage or progress state of an ongoing process, project, or development.
-
D.
roleDependsOn
Indicates that the existence, behavior, or permissions of one role are contingent upon or derived from another role.
-
E.
fateDependsOn
Indicates that the outcome or destiny of one entity is determined or significantly influenced by another entity or condition.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6babadb3481908b49400b3ab42a7c |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:35 a.m.