Triple
T27915865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | القرداحة |
E706068
|
entity |
| Predicate | governingFamilyInfluence |
P114304
|
FINISHED |
| Object | عائلة الأسد |
—
|
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: عائلة الأسد | Statement: [القرداحة, governingFamilyInfluence, عائلة الأسد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingFamilyInfluence Context triple: [القرداحة, governingFamilyInfluence, عائلة الأسد]
-
A.
familyInfluenceArea
chosen
Indicates the domain or scope within which a family exerts influence, impact, or control over something or someone.
-
B.
parentInfluence
Indicates that one entity has a formative or guiding effect on another entity in the role of a parent.
-
C.
upbringingInfluence
Indicates that one entity’s upbringing has had a formative influence on another entity’s behavior, values, or development.
-
D.
impactOnFamily
Indicates the effect or influence that something has on a family’s situation, dynamics, or well-being.
-
E.
familyAffectedBy
Indicates that one or more members of a person’s family experience or are impacted by a specified condition, event, or circumstance.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 27, 2026, 6:53 p.m.