Triple
T26754273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownlow family |
E674628
|
entity |
| Predicate | landedGentryStatus |
P52082
|
FINISHED |
| Object | landed gentry of England |
—
|
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: landed gentry of England | Statement: [Brownlow family, landedGentryStatus, landed gentry of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landedGentryStatus Context triple: [Brownlow family, landedGentryStatus, landed gentry of England]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
involvedNobility
Indicates that the entities participated in or were associated with an event, action, or situation in the capacity of nobility or aristocratic status.
-
D.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
positionOnNobility
Indicates the rank or status an entity holds within a hierarchy of nobility.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618cf64208190a3a6650683267354 |
completed | May 2, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:54 a.m.