Triple
T33326825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delilah |
E853285
|
entity |
| Predicate | navalBranchDepicted |
P157023
|
FINISHED |
| Object | United States Navy |
—
|
NE NERFINISHED |
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: United States Navy | Statement: [Delilah, navalBranchDepicted, United States Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalBranchDepicted Context triple: [Delilah, navalBranchDepicted, United States Navy]
-
A.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
B.
navalWarfareBranch
Indicates that one entity is a branch or component of naval warfare to which the other entity belongs or with which it is associated.
-
C.
NavyRegistry
Indicates a formal registration or listing of an entity within an official navy or naval organization.
-
D.
navalAffiliation
chosen
Indicates a formal relationship in which an entity is associated with, belongs to, or operates under a particular navy or naval force.
-
E.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.