Triple
T4089275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fisher House Foundation |
E87664
|
entity |
| Predicate | lodgingCostToFamilies |
P52944
|
FINISHED |
| Object | free |
—
|
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: free | Statement: [Fisher House Foundation, lodgingCostToFamilies, free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lodgingCostToFamilies Context triple: [Fisher House Foundation, lodgingCostToFamilies, free]
-
A.
numberOfFamilies
Indicates the total count of distinct family units associated with a given entity or context.
-
B.
fareStructure
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
C.
fareCalculation
Indicates the process or method used to determine the monetary cost of a trip or service based on specified pricing rules and conditions.
-
D.
familySeat
Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
-
E.
fareStructureFeature
Indicates a characteristic or condition of how fares are structured, calculated, or applied within a pricing or ticketing system.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9b34dec81909bbc3def9decc71a |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:39 p.m.