Triple
T24824614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLASH free-electron laser |
E621153
|
entity |
| Predicate | userAccessMode |
P6865
|
FINISHED |
| Object | international 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: international user facility | Statement: [FLASH free-electron laser, userAccessMode, international user facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userAccessMode Context triple: [FLASH free-electron laser, userAccessMode, international user facility]
-
A.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
B.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
C.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
D.
approximateAccessMode
Indicates that one entity can access or interact with another using a mode or method that is not exact or fully precise, but sufficiently close for the intended purpose.
-
E.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:05 a.m.