Triple
T30392646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANDU reactor technology |
E773129
|
entity |
| Predicate | moderatorLocation |
P182255
|
FINISHED |
| Object | separate low-pressure calandria |
—
|
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: separate low-pressure calandria | Statement: [CANDU reactor technology, moderatorLocation, separate low-pressure calandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moderatorLocation Context triple: [CANDU reactor technology, moderatorLocation, separate low-pressure calandria]
-
A.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
-
B.
membershipLocation
Indicates that an entity’s membership or affiliation is associated with, based in, or held at a particular location.
-
C.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 29, 2026, 8:02 p.m.