Triple
T5343021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J.A.R.V.I.S. |
E123986
|
entity |
| Predicate | nationalityStyle |
P59353
|
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: [J.A.R.V.I.S., nationalityStyle, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalityStyle Context triple: [J.A.R.V.I.S., nationalityStyle, British]
-
A.
originCountryStyle
chosen
Indicates that something is characterized by or created in the style or manner typical of a particular country of origin.
-
B.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
C.
hasNationalityTraditionally
Indicates that an entity is traditionally or historically associated with a particular nationality, regardless of current legal or formal citizenship status.
-
D.
nationalityInStory
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
-
E.
nationalityInWorld
Indicates that an entity has a specific national affiliation or citizenship within the world 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.