Triple
T10433848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESV.org |
E245984
|
entity |
| Predicate | supportsAccessModel |
P93561
|
FINISHED |
| Object | free access |
—
|
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: free access | Statement: [ESV.org, supportsAccessModel, free access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAccessModel Context triple: [ESV.org, supportsAccessModel, free access]
-
A.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
B.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
C.
supportsContributionModel
Indicates that one entity enables or is compatible with a particular model or framework for making contributions (such as donations, content, or resources).
-
D.
accessModelIntroduced
Indicates that a particular method, mechanism, or pathway for accessing something has been newly introduced or made available.
-
E.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
- F. None of above. chosen
Provenance (4 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea65afe08190b91260c9267a0f14 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:14 p.m.