Triple
T36304625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qi language |
E893910
|
entity |
| Predicate | likelyInfluencedBy |
P63713
|
FINISHED |
| Object | Chinese |
—
|
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: Chinese | Statement: [Qi language, likelyInfluencedBy, Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyInfluencedBy Context triple: [Qi language, likelyInfluencedBy, Chinese]
-
A.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
B.
wereInfluencedBy
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
C.
influenceOf
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
D.
hasPossibleInfluence
chosen
Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
-
E.
influencedByClaim
Indicates that an entity’s state, behavior, or status is affected or shaped by a specific claim.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.