Triple
T722912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habitat for Humanity International |
E14656
|
entity |
| Predicate | engages |
P1256
|
FINISHED |
| Object | volunteers |
—
|
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: volunteers | Statement: [Habitat for Humanity International, engages, volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engages Context triple: [Habitat for Humanity International, engages, volunteers]
-
A.
engagementType
Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
-
B.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
engagementArea
Indicates the spatial region or scope within which an entity’s actions, influence, or interactions are intended to occur.
-
D.
notableEngagement
Indicates a significant interaction, involvement, or participation between entities that is noteworthy or distinguished in some context.
-
E.
engagedTo
Indicates that two entities are formally committed to marry each other.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a5360c8190b16e1e4f4206d0aa |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.