Triple
T9476990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | naval intelligence |
E228539
|
entity |
| Predicate | collectsOn |
P2196
|
FINISHED |
| Object | enemy naval forces |
—
|
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: enemy naval forces | Statement: [naval intelligence, collectsOn, enemy naval forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsOn Context triple: [naval intelligence, collectsOn, enemy naval forces]
-
A.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
B.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
-
C.
collects
chosen
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
D.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
E.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd80127744819082176b2d4417216e |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.