Triple
T8599379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiang Wei |
E203634
|
entity |
| Predicate | notableCampaignDirection |
P83787
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Jiang Wei, notableCampaignDirection, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCampaignDirection Context triple: [Jiang Wei, notableCampaignDirection, north]
-
A.
notableCampaign
Indicates that an entity is prominently associated with a particular campaign, such as by leading, featuring in, or being a key focus of that campaign.
-
B.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
C.
notableRally
Indicates a rally or gathering that is distinguished by particular significance, impact, or prominence compared to ordinary rallies.
-
D.
notableInitiative
Indicates that an entity is especially recognized for leading, launching, or being closely associated with a significant project, program, or initiative.
-
E.
notableProponent
Indicates that an entity is a well-known advocate or supporter of another entity, idea, or practice.
- F. None of above. chosen
Provenance (4 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d7c184819083236c75f9ccc9cf |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:24 p.m.