Triple
T19698532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India in World Politics |
E473029
|
entity |
| Predicate | notableAuthorIs |
P74630
|
FINISHED |
| Object | Indian revolutionary |
—
|
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: Indian revolutionary | Statement: [India in World Politics, notableAuthorIs, Indian revolutionary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAuthorIs Context triple: [India in World Politics, notableAuthorIs, Indian revolutionary]
-
A.
notableAuthorAttribute
Indicates that a particular attribute or characteristic is especially notable or significant for an author in the context of their work or recognition.
-
B.
notableAuthorMember
chosen
Indicates that an entity is a notable or distinguished author who is a member of a particular group, organization, or collection.
-
C.
notableAuthorMention
Indicates that a notable or well-known author is referenced or cited in relation to the subject.
-
D.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
E.
notableAuthorPublished
Indicates that a work was published by an author who is recognized as notable or distinguished.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b2baec81909ee2cd6ead632836 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.