Triple
T21115834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICT 1201 |
E520295
|
entity |
| Predicate | computingGeneration |
P9898
|
FINISHED |
| Object | second generation |
—
|
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: second generation | Statement: [ICT 1201, computingGeneration, second generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingGeneration Context triple: [ICT 1201, computingGeneration, second generation]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
technologyGeneration
chosen
Indicates the generational level or era of technology associated with or used by an entity in relation to another.
-
C.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
D.
generationOf
Indicates that one entity is the origin, creator, or producer of another entity.
-
E.
mainGenerationTechnology
Indicates the primary technology or method used to generate something, typically identifying the dominant production or generation approach among possible alternatives.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72105bd648190beecc636284397bd |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:55 p.m.