Triple
T11094032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bride |
E262327
|
entity |
| Predicate | writerNationality |
P6689
|
FINISHED |
| Object | Scottish |
—
|
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: Scottish | Statement: [The Bride, writerNationality, Scottish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writerNationality Context triple: [The Bride, writerNationality, Scottish]
-
A.
authorNationality
chosen
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
B.
creatorNationality
Indicates that the creator of an entity has a specified national affiliation or citizenship.
-
C.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
-
D.
writtenInCountry
Indicates that a written work was created, authored, or composed within the geographical boundaries of a specific country.
-
E.
nationalityInStory
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ed12d88190a4ad8c346d68f11f |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.