Triple
T16655628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Code |
E404719
|
entity |
| Predicate | mayReference |
P1775
|
FINISHED |
| Object | building code |
—
|
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: building code | Statement: [Fire Code, mayReference, building code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayReference Context triple: [Fire Code, mayReference, building code]
-
A.
mayReferMattersTo
Indicates that one party has the option or authority to direct or escalate certain issues, cases, or concerns to another party or body for consideration or action.
-
B.
mayEntail
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
-
C.
canRefer
chosen
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
mayDirect
Indicates that one entity has the permission or authority to direct, manage, or oversee the actions or operations of another entity.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfa45d8819081bf8579a7160389 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.