Triple
T34172246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caine family |
E876574
|
entity |
| Predicate | hasEthnicOrNationalBackground |
P159764
|
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: [Caine family, hasEthnicOrNationalBackground, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicOrNationalBackground Context triple: [Caine family, hasEthnicOrNationalBackground, British]
-
A.
hasEthnicOrRegionalOrigin
chosen
Indicates that an entity originates from, or is associated with, a particular ethnic group or geographic region.
-
B.
hasEthnicOrNationalComposition
Indicates that an entity is characterized by a particular ethnic or national group composition.
-
C.
hasEthnicClassificationHistory
Indicates that an entity has a recorded history of changes or assignments in its ethnic classification over time.
-
D.
hasMajorEthnicMinority
Indicates that an entity includes a significant ethnic minority group within its overall population or composition.
-
E.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.