Triple
T6231375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WikiWikiWeb |
E139360
|
entity |
| Predicate | topicHasInfluenced |
P63153
|
FINISHED |
| Object | wiki concept |
—
|
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 concept | Statement: [WikiWikiWeb, topicHasInfluenced, wiki concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topicHasInfluenced Context triple: [WikiWikiWeb, topicHasInfluenced, wiki concept]
-
A.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
-
B.
hasSignificantInfluenceIn
chosen
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
C.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
eventInfluencedBy
Indicates that an event occurs or unfolds in a way that is causally or significantly affected by another entity, factor, or prior event.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ec5be4819084d6df2e8dd2a542 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.