Triple
T34770930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maqdas |
E1002358
|
entity |
| Predicate | accessPrerequisite |
P117576
|
FINISHED |
| Object | ordination |
—
|
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: ordination | Statement: [maqdas, accessPrerequisite, ordination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessPrerequisite Context triple: [maqdas, accessPrerequisite, ordination]
-
A.
accessPrinciple
Indicates that one entity has the right, ability, or method to obtain, use, or interact with another entity or resource under defined conditions.
-
B.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
C.
administrationRequirement
Indicates that a certain action, process, or entity must be overseen, approved, or carried out by an administrative authority or according to administrative rules.
-
D.
assuredAccessRequirement
chosen
Indicates that one entity requires guaranteed, reliable access to another entity, resource, or service as a condition or constraint.
-
E.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 3:59 p.m.