Triple
T230795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LHCf |
E4405
|
entity |
| Predicate | studiesForwardRegion |
P9518
|
FINISHED |
| Object | pseudorapidity greater than 8 |
—
|
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: pseudorapidity greater than 8 | Statement: [LHCf, studiesForwardRegion, pseudorapidity greater than 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesForwardRegion Context triple: [LHCf, studiesForwardRegion, pseudorapidity greater than 8]
-
A.
searchesRegion
Indicates that an entity performs a search operation within, or targeting, a specified geographic or administrative region.
-
B.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
C.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
D.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
E.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e0868708190ad551ca06cc57f4a |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b5a075081909b0e9b88c1492d5a |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.