Triple
T26253175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moncreiffe House |
E656650
|
entity |
| Predicate | hasAssociatedClan |
P1915
|
FINISHED |
| Object | Clan Moncreiffe |
—
|
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 Moncreiffe | Statement: [Moncreiffe House, hasAssociatedClan, Clan Moncreiffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedClan Context triple: [Moncreiffe House, hasAssociatedClan, Clan Moncreiffe]
-
A.
associatedClan
chosen
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
B.
hasSubclan
Indicates that one clan contains or is composed of a smaller, subordinate clan within its structure.
-
C.
hasClanStatus
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
D.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
-
E.
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.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 9:07 p.m.