Triple
T35315302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robertson of Lude |
E1019886
|
entity |
| Predicate | sharesClanChiefWith |
P202170
|
FINISHED |
| Object | Clan Robertson |
—
|
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: Clan Robertson | Statement: [Robertson of Lude, sharesClanChiefWith, Clan Robertson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesClanChiefWith Context triple: [Robertson of Lude, sharesClanChiefWith, Clan Robertson]
-
A.
sharesClanBadgeWith
Indicates that two entities possess and display the same clan badge, signifying shared clan affiliation or membership.
-
B.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
-
C.
sharesCliffWith
Indicates that two entities occupy or are associated with the same cliff or cliffside area.
-
D.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
E.
hasChiefClan
Indicates that one entity serves as the primary or leading clan associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
| PDg | Predicate description generation | batch_6a005be3afb481908a2a4646e41e1004 |
completed | May 10, 2026, 10:20 a.m. |
Created at: May 3, 2026, 4:03 p.m.