Triple
T4396807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svan culture |
E99510
|
entity |
| Predicate | socialUnit |
P6110
|
FINISHED |
| Object | large patrilineal families |
—
|
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: large patrilineal families | Statement: [Svan culture, socialUnit, large patrilineal families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialUnit Context triple: [Svan culture, socialUnit, large patrilineal families]
-
A.
socialComposition
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
B.
socialCenter
Indicates that a place functions as a primary gathering point or hub for social interaction and community activities.
-
C.
socialView
Indicates a relationship where one entity views, accesses, or inspects another entity’s social-related information, profile, or activity.
-
D.
socialBase
chosen
Indicates a foundational social relationship or structure that underlies or supports interactions between entities.
-
E.
socialContribution
Indicates that an entity engages in actions or provides resources that benefit society or a community beyond its own direct interests.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352aca86c8190b5af7e6600072066 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:20 p.m.