Triple
T37505957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant (U.S. Navy) |
E932091
|
entity |
| Predicate | commonAddress |
P174316
|
FINISHED |
| Object | Lieutenant |
—
|
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: Lieutenant | Statement: [Lieutenant (U.S. Navy), commonAddress, Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAddress Context triple: [Lieutenant (U.S. Navy), commonAddress, Lieutenant]
-
A.
helpsAddress
Indicates that one entity contributes to solving, mitigating, or dealing with an issue, need, or problem associated with another entity.
-
B.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
C.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
D.
addressesPillar
Indicates that one entity directly deals with, responds to, or supports a specific foundational pillar or core focus area of another entity or framework.
-
E.
addressedWith
chosen
Indicates that one entity is referred to or spoken to using a particular name, title, or form of address.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 4:17 p.m.