Triple
T24279409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvalangadu plates |
E605497
|
entity |
| Predicate | mentionsCampaign |
P831
|
FINISHED |
| Object | Ganges expedition of Rajendra I |
—
|
NE NERFINISHED |
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: Ganges expedition of Rajendra I | Statement: [Tiruvalangadu plates, mentionsCampaign, Ganges expedition of Rajendra I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsCampaign Context triple: [Tiruvalangadu plates, mentionsCampaign, Ganges expedition of Rajendra I]
-
A.
campaignMentionedIn
Indicates that a campaign is referenced or discussed within a particular document, message, or piece of content.
-
B.
mentionsSee
Indicates that one entity explicitly refers to or cites another entity within its content.
-
C.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
D.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
E.
supportedCampaignOf
Indicates that one entity actively backed, promoted, or provided assistance to the campaign associated with another entity.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f51050481908a9bd3c586702057 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.