Triple
T30376857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrian human rights organizations |
E772713
|
entity |
| Predicate | oftenBasedIn |
P93876
|
FINISHED |
| Object | Syrian diaspora communities |
—
|
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: Syrian diaspora communities | Statement: [Syrian human rights organizations, oftenBasedIn, Syrian diaspora communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenBasedIn Context triple: [Syrian human rights organizations, oftenBasedIn, Syrian diaspora communities]
-
A.
isTypicallyBasedIn
chosen
Indicates that one entity is most commonly located, headquartered, or primarily operates within the context or place specified by another entity.
-
B.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
-
C.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
D.
residencyOf
Indicates that one entity serves as the place where another entity resides or lives.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 8 p.m.