Triple
T6099764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunga Din |
E135963
|
entity |
| Predicate | portrayalOfGungaDin |
P68120
|
FINISHED |
| Object | brave |
—
|
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: brave | Statement: [Gunga Din, portrayalOfGungaDin, brave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayalOfGungaDin Context triple: [Gunga Din, portrayalOfGungaDin, brave]
-
A.
portraysPurushaAs
Indicates that one entity represents or depicts another entity as Purusha, the cosmic or primordial being.
-
B.
portrayalFeature
Indicates that one entity serves as a characteristic, aspect, or attribute highlighted in the depiction or representation of another entity.
-
C.
portrayalRecognition
Indicates that one entity recognizes or identifies another entity as a portrayal or representation of a particular subject or character.
-
D.
portraysFictionalEntity
Indicates that one entity depicts, represents, or plays the role of a fictional character or figure.
-
E.
wasPortrayedAs
Indicates that one entity has been depicted or represented in the form or role of another entity, typically within some medium or context.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.