Triple
T22695686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILD detector concept |
E561165
|
entity |
| Predicate | interactionRegion |
P5347
|
FINISHED |
| Object | central interaction point of the ILC |
—
|
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: central interaction point of the ILC | Statement: [ILD detector concept, interactionRegion, central interaction point of the ILC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionRegion Context triple: [ILD detector concept, interactionRegion, central interaction point of the ILC]
-
A.
interactionPoint
chosen
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
B.
selectionRegion
Indicates a relationship where a specific region or area is designated as the active selection within a larger space or context.
-
C.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
D.
impactRegion
Indicates the geographic or spatial area that is affected or influenced by a particular event, action, or phenomenon.
-
E.
trackRegion
Indicates that an entity is associated with, occurs within, or is relevant to a specific geographic or logical region used for tracking.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789e05d88190b9d51bb3f8e3e9d4 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:14 p.m.