Triple
T23154829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C2 wiki |
E578410
|
entity |
| Predicate | hasInfluencedTerm |
P9129
|
FINISHED |
| Object | wiki |
—
|
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: wiki | Statement: [C2 wiki, hasInfluencedTerm, wiki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfluencedTerm Context triple: [C2 wiki, hasInfluencedTerm, wiki]
-
A.
hasEnduringInfluenceOn
Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
-
B.
hadInfluenceOn
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
-
C.
hasLexicalInfluenceOn
chosen
Indicates that one linguistic element (such as a word, phrase, or lexicon) has affected or shaped the form, usage, or meaning of another linguistic element.
-
D.
influencedNameOf
Indicates that one entity has affected or shaped the naming or choice of name of another entity.
-
E.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
- 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.