Triple
T6146586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H8 beam line |
E137092
|
entity |
| Predicate | supportsPhysics |
P69440
|
FINISHED |
| Object | hadron 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: hadron physics | Statement: [H8 beam line, supportsPhysics, hadron physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPhysics Context triple: [H8 beam line, supportsPhysics, hadron physics]
-
A.
includesPhysicalWorld
Indicates that one entity encompasses, contains, or incorporates aspects or elements of the physical world within its scope or definition.
-
B.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cdeeaa88190948d9db6eb2dbf46 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:16 p.m.