Triple
T4468541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN HiRadMat facility |
E98437
|
entity |
| Predicate | servesProject |
P12986
|
FINISHED |
| Object | LHC machine protection studies |
—
|
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: LHC machine protection studies | Statement: [CERN HiRadMat facility, servesProject, LHC machine protection studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesProject Context triple: [CERN HiRadMat facility, servesProject, LHC machine protection studies]
-
A.
servesProgram
Indicates that one entity provides services or functions in support of a particular program.
-
B.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
C.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
D.
supportsProject
chosen
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
-
E.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.