Triple
T4828406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Linear Collider |
E107881
|
entity |
| Predicate | acceleratorTechnology |
P17456
|
FINISHED |
| Object | linear accelerator |
—
|
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: linear accelerator | Statement: [Stanford Linear Collider, acceleratorTechnology, linear accelerator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceleratorTechnology Context triple: [Stanford Linear Collider, acceleratorTechnology, linear accelerator]
-
A.
acceleratorType
chosen
Indicates the kind or category of accelerator associated with or used by an entity.
-
B.
mainGenerationTechnology
Indicates the primary technology or method used to generate something, typically identifying the dominant production or generation approach among possible alternatives.
-
C.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
D.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
E.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.