Triple
T17137985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laxgibuu |
E415888
|
entity |
| Predicate | hasSocialStructureElement |
P8216
|
FINISHED |
| Object | houses (wilp) |
—
|
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: houses (wilp) | Statement: [Laxgibuu, hasSocialStructureElement, houses (wilp)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialStructureElement Context triple: [Laxgibuu, hasSocialStructureElement, houses (wilp)]
-
A.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
E.
hasSocialDimension
Indicates that the relationship, attribute, or phenomenon involves social aspects, interactions, or implications among individuals or groups.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d1277881909325ffd2a7aa4873 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.