Triple
T11056621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALS |
E261391
|
entity |
| Predicate | userFacilityType |
P38239
|
FINISHED |
| Object | open-access scientific user facility |
—
|
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: open-access scientific user facility | Statement: [ALS, userFacilityType, open-access scientific user facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userFacilityType Context triple: [ALS, userFacilityType, open-access scientific user facility]
-
A.
userFacility
chosen
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
B.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
D.
usedAtFacilityType
Indicates that something is utilized or applied within a facility of a specified type.
-
E.
campusFacilityType
Indicates the specific kind of facility a campus location is classified as (e.g., library, laboratory, residence hall).
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2404c819090cb0825a67a64fa |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.