Triple
T36920704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rundown pub |
E913189
|
entity |
| Predicate | mayComplyWith |
P186691
|
FINISHED |
| Object | basic licensing regulations |
—
|
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: basic licensing regulations | Statement: [Rundown pub, mayComplyWith, basic licensing regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayComplyWith Context triple: [Rundown pub, mayComplyWith, basic licensing regulations]
-
A.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
B.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
C.
mayApprove
Indicates that an entity has the authority or permission to approve another entity or action, but is not required to do so.
-
D.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
E.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.