Triple
T35824477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cora (Império) |
E1035599
|
entity |
| Predicate | hasNationalityInStoryWorld |
P15237
|
FINISHED |
| Object | Brazilian |
—
|
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: Brazilian | Statement: [Cora (Império), hasNationalityInStoryWorld, Brazilian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalityInStoryWorld Context triple: [Cora (Império), hasNationalityInStoryWorld, Brazilian]
-
A.
nationalityInStory
chosen
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
-
B.
nationalityInHumanWorld
Indicates that one entity has the specified national affiliation or citizenship within the context of the human world.
-
C.
nationalityInWorld
Indicates that an entity has a specific national affiliation or citizenship within the world context.
-
D.
nationalityOfFictionalSetting
Indicates that a fictional setting is associated with, or belongs to, a particular nationality or country.
-
E.
isByNationality
Indicates that one entity has a specified nationality or originates from the country represented by the other 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4:06 p.m.