Triple
T22242316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franciscan Health Lafayette |
E549752
|
entity |
| Predicate | belongsToNetworkType |
P71779
|
FINISHED |
| Object | regional hospital network |
—
|
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: regional hospital network | Statement: [Franciscan Health Lafayette, belongsToNetworkType, regional hospital network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNetworkType Context triple: [Franciscan Health Lafayette, belongsToNetworkType, regional hospital network]
-
A.
inUniverseNetworkType
Indicates that one entity has a specific type or category of network within a particular fictional or defined universe in relation to another entity.
-
B.
basedOnNetwork
Indicates that something is determined, derived, or operates according to a particular network or network-related characteristics.
-
C.
belongsToSystemType
chosen
Indicates that one entity is classified under, or is a member of, a particular system type.
-
D.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
E.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132150a3c81908eba0683819e26d0 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.