Triple
T2064483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little France |
E45865
|
entity |
| Predicate | hasMajorFacilityType |
P2836
|
FINISHED |
| Object | teaching hospital |
—
|
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: teaching hospital | Statement: [Little France, hasMajorFacilityType, teaching hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorFacilityType Context triple: [Little France, hasMajorFacilityType, teaching hospital]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
-
C.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
-
D.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or place).
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d5147c8190a264fe42f0634cec |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.