Triple
T35285178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacLemmon |
E1019059
|
entity |
| Predicate | hasClanHeritage |
P176968
|
FINISHED |
| Object | Lamont clan heritage |
—
|
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: Lamont clan heritage | Statement: [MacLemmon, hasClanHeritage, Lamont clan heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClanHeritage Context triple: [MacLemmon, hasClanHeritage, Lamont clan heritage]
-
A.
hasClanMother
Indicates that an individual belongs to or is under the authority or lineage of a specific clan mother within a clan-based social structure.
-
B.
hasSubclan
Indicates that one clan contains or is composed of a smaller, subordinate clan within its structure.
-
C.
hasHereditaryLegacy
Indicates that an entity possesses a legacy, status, or attribute that is passed down through familial or ancestral inheritance.
-
D.
hasBloodline
chosen
Indicates that one entity is ancestrally or genetically descended from, or belongs to the lineage of, another entity.
-
E.
clanInheritance
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:03 p.m.