Triple
T148310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spencer-Churchill family |
E3375
|
entity |
| Predicate | hasLineageFrom |
P369
|
FINISHED |
| Object | English gentry |
—
|
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: English gentry | Statement: [Spencer-Churchill family, hasLineageFrom, English gentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineageFrom Context triple: [Spencer-Churchill family, hasLineageFrom, English gentry]
-
A.
hasAncestor
chosen
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
B.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
E.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ecb6f48190992c4c8ca908a81c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.