Triple
T689256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scratch Foundation |
E13353
|
entity |
| Predicate | supportsOpenAccess |
P1390
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Scratch Foundation, supportsOpenAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOpenAccess Context triple: [Scratch Foundation, supportsOpenAccess, true]
-
A.
openAccessPolicy
chosen
Indicates that an entity has a policy allowing unrestricted or minimally restricted public access to its resources, content, or services.
-
B.
supportsOpenLoopPayments
Indicates that an entity enables or is compatible with open-loop payment methods, where transactions are processed over general-purpose payment networks rather than a closed, proprietary system.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
E.
openAccessDelay
Indicates the length of time between an item’s initial restricted publication and when it becomes freely accessible to the public.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.