Triple
T11164869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | actinide series |
E264133
|
entity |
| Predicate | hasKeyApplication |
P14571
|
FINISHED |
| Object | nuclear energy |
—
|
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: nuclear energy | Statement: [actinide series, hasKeyApplication, nuclear energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyApplication Context triple: [actinide series, hasKeyApplication, nuclear energy]
-
A.
hasApp
chosen
Indicates that an entity possesses, provides, or is associated with a particular application.
-
B.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of application.
-
C.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
D.
keyApplication
Indicates that an application or software program serves as the primary or central tool used for a particular purpose or function.
-
E.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e887293081909830852000d533fa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.