Triple
T35480473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhailo-Bhailo house-visiting tradition |
E1025455
|
entity |
| Predicate | hostsOffer |
P129222
|
FINISHED |
| Object | money |
—
|
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: money | Statement: [Bhailo-Bhailo house-visiting tradition, hostsOffer, money]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsOffer Context triple: [Bhailo-Bhailo house-visiting tradition, hostsOffer, money]
-
A.
hostsNearby
Indicates that one entity serves as a host located in close physical proximity to another entity.
-
B.
boardingOffered
Indicates that the provision of boarding or lodging services is being made available to one or more entities.
-
C.
hostRover
Indicates that one entity serves as the host, base, or platform for a rover, supporting its presence or operation.
-
D.
hostsAt
Indicates that one entity provides the venue or location where an event, activity, or other entity takes place.
-
E.
offeredOver
chosen
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.