Triple
T8749803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Launfal |
E207927
|
entity |
| Predicate | showsCharityTo |
P85174
|
FINISHED |
| Object | a leper |
—
|
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: a leper | Statement: [Sir Launfal, showsCharityTo, a leper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsCharityTo Context triple: [Sir Launfal, showsCharityTo, a leper]
-
A.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
B.
charityComponent
Indicates that one entity functions as a charitable element, feature, or part within another entity or larger arrangement.
-
C.
hasCharitySingle
Indicates that an entity is associated with exactly one specific charitable organization or charitable initiative.
-
D.
philanthropicInitiative
Indicates an action or relationship where an entity undertakes or supports activities intended to promote the welfare of others, typically through charitable or socially beneficial efforts.
-
E.
hasCharityConnection
Indicates a relationship in which one entity is connected to another through charitable activities, support, or affiliation.
- F. None of above. chosen
Provenance (4 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da5d474819084ae81d21a5089fa |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:39 p.m.