Triple
T28946803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Residents controlled finance |
E730601
|
entity |
| Predicate | typicalResidentTitle |
P85416
|
FINISHED |
| Object | British Resident |
—
|
NE NERFINISHED |
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 Resident | Statement: [British Residents controlled finance, typicalResidentTitle, British Resident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResidentTitle Context triple: [British Residents controlled finance, typicalResidentTitle, British Resident]
-
A.
typicalOfficeHolderTitle
chosen
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
B.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
commonTitle
Indicates that two or more entities share the same title or designation.
-
D.
primaryUserTitle
Indicates the main professional or role-based title associated with a user in a given context.
-
E.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: April 28, 2026, 8:40 a.m.