Triple
T23154800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C2 wiki |
E578410
|
entity |
| Predicate | originalSoftware |
P145344
|
FINISHED |
| Object | WikiWikiWeb engine |
—
|
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: WikiWikiWeb engine | Statement: [C2 wiki, originalSoftware, WikiWikiWeb engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSoftware Context triple: [C2 wiki, originalSoftware, WikiWikiWeb engine]
-
A.
originProgram
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
B.
developedSoftware
chosen
Indicates that one entity created, programmed, or significantly contributed to the creation of a particular software system or application for another entity or purpose.
-
C.
originalSample
Indicates that one entity serves as the initial or source sample from which another related sample or derivative is obtained or based.
-
D.
originalProgrammingFor
Indicates that one entity is the initial or primary creator or producer of programming content for another entity.
-
E.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.