Triple
T13108227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Engineering and Radiological Sciences |
E310903
|
entity |
| Predicate | integratesFrom |
P63881
|
FINISHED |
| Object | physics |
—
|
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: physics | Statement: [Nuclear Engineering and Radiological Sciences, integratesFrom, physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesFrom Context triple: [Nuclear Engineering and Radiological Sciences, integratesFrom, physics]
-
A.
integratedFrom
chosen
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
B.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
C.
incorporatedFrom
Indicates that one entity was formed, established, or legally created by deriving or transforming from another pre-existing entity.
-
D.
integratesOn
Indicates that one entity is designed to work seamlessly within, or be combined functionally with, another entity or platform.
-
E.
implementedFrom
Indicates that one entity is realized, built, or executed based on the design, specification, or definition provided by another entity.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817ce07881909ec552bf861ac175 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.