Triple
T10624604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3RC |
E250289
|
entity |
| Predicate | associatedWithBeam |
P6098
|
FINISHED |
| Object | 58.8 m |
—
|
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: 58.8 m | Statement: [H3RC, associatedWithBeam, 58.8 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBeam Context triple: [H3RC, associatedWithBeam, 58.8 m]
-
A.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
B.
associatedWithParticle
Indicates that an entity has a contextual or functional connection to a specific particle (such as a subatomic particle or grammatical particle).
-
C.
hasTypicalBeam
chosen
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
D.
associatedWithPub
Indicates that an entity has a connection or relationship with a particular publication (e.g., as source, reference, or related work).
-
E.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.