Triple
T18896820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RPI Engineers women's ice hockey |
E462228
|
entity |
| Predicate | hasHomeFacilityType |
P2836
|
FINISHED |
| Object | indoor ice arena |
—
|
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: indoor ice arena | Statement: [RPI Engineers women's ice hockey, hasHomeFacilityType, indoor ice arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeFacilityType Context triple: [RPI Engineers women's ice hockey, hasHomeFacilityType, indoor ice arena]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
C.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
D.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
hasFacilityLevel
Indicates the degree or tier of capability, service, or infrastructure that a particular facility possesses.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c47f6c948190918ade08bb88f1fd |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.