Triple
T9148449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalie |
E219519
|
entity |
| Predicate | hasFictionalNationality |
P15237
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [Natalie, hasFictionalNationality, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalNationality Context triple: [Natalie, hasFictionalNationality, British]
-
A.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
-
B.
countryOfOriginFictional
Indicates that a fictional work, character, or element originates from or is associated with a particular country within its narrative or setting.
-
C.
nationalityInStory
chosen
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
-
D.
hasFictionalAlias
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
E.
hasFictionalProperty
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca91a1fd08190a5bb3d9280439b09 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.