Triple
T5767112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALEPH |
E127241
|
entity |
| Predicate | subdetector |
P28620
|
FINISHED |
| Object | vertex detector |
—
|
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: vertex detector | Statement: [ALEPH, subdetector, vertex detector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdetector Context triple: [ALEPH, subdetector, vertex detector]
-
A.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
numberOfMainDetectors
Indicates the quantity of primary detectors associated with or used in a given context or system.
-
D.
subsurfaceSamplingDevice
Indicates a device is used to collect or sample materials from beneath a surface, such as soil, rock, or sediment layers.
-
E.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.