Triple
T17106945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Training, Research, Isotopes, General Atomics |
E415124
|
entity |
| Predicate | coreLocation |
P125949
|
FINISHED |
| Object | open pool of water |
—
|
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: open pool of water | Statement: [Training, Research, Isotopes, General Atomics, coreLocation, open pool of water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreLocation Context triple: [Training, Research, Isotopes, General Atomics, coreLocation, open pool of water]
-
A.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
baseLocation
Indicates the primary place where an entity is based, headquartered, or operates from as its main location.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2750b481908de18e8cb8f2195c |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.