Triple
T36076910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEX 45D |
E1043519
|
entity |
| Predicate | hasAccessControlType |
P47431
|
FINISHED |
| Object | grade-separated |
—
|
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: grade-separated | Statement: [MEX 45D, hasAccessControlType, grade-separated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessControlType Context triple: [MEX 45D, hasAccessControlType, grade-separated]
-
A.
hasSecurityAccessControl
Indicates that an entity enforces or is associated with mechanisms that regulate and control access to resources or information for security purposes.
-
B.
hasAccessConstraint
chosen
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
-
C.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
D.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
E.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:08 p.m.