Triple
T36824846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urretxu |
E909981
|
entity |
| Predicate | linkedSociallyWith |
P165031
|
FINISHED |
| Object | Zumarraga |
—
|
NE NERFINISHED |
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: Zumarraga | Statement: [Urretxu, linkedSociallyWith, Zumarraga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedSociallyWith Context triple: [Urretxu, linkedSociallyWith, Zumarraga]
-
A.
deFactoLinkedWith
Indicates that two entities are informally or practically associated or connected, even if there is no official or legally recognized relationship between them.
-
B.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
C.
hasSocialTieWith
Indicates a social relationship or connection exists between two entities, such as friendship, acquaintance, or other interpersonal tie.
-
D.
socialLink
chosen
Indicates that there exists a social relationship or connection between the referenced entities, such as friendship, following, or other social-network ties.
-
E.
socialProfile
Indicates that an entity has an associated social media or online networking profile.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:13 p.m.