Triple
T26455049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEPO research reactor |
E665459
|
entity |
| Predicate | hasResearchType |
P36094
|
FINISHED |
| Object | experimental reactor |
—
|
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: experimental reactor | Statement: [BEPO research reactor, hasResearchType, experimental reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchType Context triple: [BEPO research reactor, hasResearchType, experimental reactor]
-
A.
hasTypeOfResearch
chosen
Indicates that an entity is associated with a particular category or kind of research it involves or conducts.
-
B.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
-
C.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
D.
hasResearcherType
Indicates that an entity is associated with a researcher characterized by a specific type or category of research role.
-
E.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 12:08 a.m.