Triple
T528771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peerage of England |
E10981
|
entity |
| Predicate | hasHigherRankThan |
P4476
|
FINISHED |
| Object | 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: gentry of England | Statement: [Peerage of England, hasHigherRankThan, gentry of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherRankThan Context triple: [Peerage of England, hasHigherRankThan, gentry of England]
-
A.
hasHigherClass
chosen
Indicates that one entity belongs to a higher rank, level, or category in a hierarchy than another entity.
-
B.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
-
C.
nextHigherRank
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
D.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
-
E.
hasHigherJurisdiction
Indicates that one authority or legal body possesses superior legal power or decision-making control over another within a defined domain or scope.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.