Triple
T20420488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabella of Lusignan |
E500833
|
entity |
| Predicate | isConnectedThroughLineageTo |
P124948
|
FINISHED |
| Object | Crusader nobility |
—
|
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: Crusader nobility | Statement: [Isabella of Lusignan, isConnectedThroughLineageTo, Crusader nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedThroughLineageTo Context triple: [Isabella of Lusignan, isConnectedThroughLineageTo, Crusader nobility]
-
A.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
B.
lineageRelatedTo
chosen
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
C.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
D.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
E.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba39f7081909358f1103a0f241c |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.