Triple
T37731290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Percy |
E940160
|
entity |
| Predicate | customaryAssociation |
P44442
|
FINISHED |
| Object | Northumberland estates |
—
|
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: Northumberland estates | Statement: [Baron Percy, customaryAssociation, Northumberland estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customaryAssociation Context triple: [Baron Percy, customaryAssociation, Northumberland estates]
-
A.
traditionAssociatesWith
Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
-
B.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
C.
customsAssociated
Indicates that certain cultural or social customs are connected with, practiced by, or characteristic of a particular entity.
-
D.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
-
E.
hasTraditionalAssociation
chosen
Indicates that one entity is customarily or historically linked with another according to tradition or long-established practice.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.