Triple
T2198088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Alberta |
E50422
|
entity |
| Predicate | fieldTestLocation |
P21652
|
FINISHED |
| Object | Tinian bomb assembly facilities |
—
|
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: Tinian bomb assembly facilities | Statement: [Project Alberta, fieldTestLocation, Tinian bomb assembly facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldTestLocation Context triple: [Project Alberta, fieldTestLocation, Tinian bomb assembly facilities]
-
A.
testLocation
chosen
Indicates the place or environment where a test, examination, or experimental procedure is conducted.
-
B.
radarLocation
Indicates the geographic position where a radar system is installed or operating.
-
C.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
D.
transmitterLocation
Indicates the spatial position or place where a transmitter is situated or operates.
-
E.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbf7b65cc8190bcc5a5c52b90f33b |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.