Triple
T38365967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Lake Erie squadron |
E892440
|
entity |
| Predicate | assembledFor |
P190467
|
FINISHED |
| Object | contest control of Lake Erie |
—
|
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: contest control of Lake Erie | Statement: [British Lake Erie squadron, assembledFor, contest control of Lake Erie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assembledFor Context triple: [British Lake Erie squadron, assembledFor, contest control of Lake Erie]
-
A.
assembledDuring
Indicates that one entity is put together or constructed within the time period of another event or process.
-
B.
assembledAt
Indicates that one entity was put together or constructed at a specific location or facility.
-
C.
isAssemblyOf
Indicates that one entity is composed of, or formed by assembling, multiple other entities into a whole.
-
D.
assembledNearEndOf
Indicates that one entity is put together or constructed in close proximity to the endpoint or final section of another entity.
-
E.
finalAssemblyBy
Indicates that one entity is responsible for performing the last stage of assembling or putting together another entity.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fcc7a42f68819081d6ec8bb6b53438 |
completed | May 7, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:31 p.m.