Triple
T6192335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oswiecim, Israel (Kfar HaOrenim) |
E138420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | symbolic partner community |
C4404
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: symbolic partner community Context triple: [Oswiecim, Israel (Kfar HaOrenim), instanceOf, symbolic partner community]
-
A.
human partnership
A human partnership is a collaborative relationship between two or more people who share goals, responsibilities, and mutual support to achieve common outcomes.
-
B.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
C.
community hub
chosen
A community hub is a central place, physical or virtual, where people gather to connect, share resources, collaborate, and participate in activities that support collective well-being and local engagement.
-
D.
collaborator
A collaborator is an individual or entity that works jointly with others, sharing responsibilities and resources to achieve a common goal or complete a shared task.
-
E.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
- F. None of above.
Provenance (1 batch)
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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:19 p.m.