Triple
T33264925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Folio |
E851617
|
entity |
| Predicate | hasTypeOfAuthorization |
P70275
|
FINISHED |
| Object | partly unauthorized |
—
|
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: partly unauthorized | Statement: [False Folio, hasTypeOfAuthorization, partly unauthorized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAuthorization Context triple: [False Folio, hasTypeOfAuthorization, partly unauthorized]
-
A.
typeOfAuthorization
chosen
Indicates the specific kind or category of authorization that applies to an action, resource, or relationship between entities.
-
B.
hasAuthorType
Indicates that an entity is associated with an author characterized by a specific role, category, or type.
-
C.
hasApprovalType
Indicates that an entity is associated with a specific category or kind of approval it has received or requires.
-
D.
hasAuthorityOf
Indicates that one entity possesses and can exercise the official power, rights, or control that properly belong to another entity.
-
E.
hasPublicAuthorityType
Indicates that an entity possesses a specific type or category of public authority status or role.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:32 a.m.