Triple
T35313495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | wasCoordinatedAt |
P164248
|
FINISHED |
| Object | Bletchley Park |
—
|
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: Bletchley Park | Statement: [ULTRA, wasCoordinatedAt, Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCoordinatedAt Context triple: [ULTRA, wasCoordinatedAt, Bletchley Park]
-
A.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
B.
coordinatedWithin
Indicates that one entity’s actions, processes, or states are organized and aligned in time or structure within the scope or framework defined by another entity.
-
C.
wasPerformedAt
chosen
Indicates that an action or event took place at a specific location or venue.
-
D.
coordinatedUnder
Indicates that one entity is organized, directed, or managed under the authority or coordination of another entity.
-
E.
coordinatedAtLevel
Indicates that two or more entities are organized or aligned to operate at the same hierarchical or functional level within a system or structure.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.