Triple
T1519479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Administrative Code |
E32193
|
entity |
| Predicate | digitalAccessURL |
P6055
|
FINISHED |
| Object | https://www.flrules.org |
—
|
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: https://www.flrules.org | Statement: [Florida Administrative Code, digitalAccessURL, https://www.flrules.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalAccessURL Context triple: [Florida Administrative Code, digitalAccessURL, https://www.flrules.org]
-
A.
accessURL
chosen
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
B.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
C.
digitalProduct
Indicates that one entity is a product that exists in digital form or is delivered electronically rather than physically.
-
D.
mediaAccess
Indicates that one entity has the ability, permission, or means to view, use, or interact with a particular media resource.
-
E.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.