Triple
T20865274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross Creek |
E513744
|
entity |
| Predicate | hasSocialDynamic |
P38895
|
FINISHED |
| Object | underlying tensions |
—
|
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: underlying tensions | Statement: [Cross Creek, hasSocialDynamic, underlying tensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialDynamic Context triple: [Cross Creek, hasSocialDynamic, underlying tensions]
-
A.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
-
B.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
C.
hasSocialDimension
chosen
Indicates that the relationship, attribute, or phenomenon involves social aspects, interactions, or implications among individuals or groups.
-
D.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
E.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45fbfc88190914c5133aa4b242c |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.