Triple
T31150342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian |
E794053
|
entity |
| Predicate | mayBeInformal |
P70028
|
FINISHED |
| Object | honorific title |
—
|
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: honorific title | Statement: [Guardian, mayBeInformal, honorific title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeInformal Context triple: [Guardian, mayBeInformal, honorific title]
-
A.
hasInformalStatus
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
B.
isLessFormalThan
Indicates that one entity has a lower level of formality or is more casual in style, tone, or usage compared to another entity.
-
C.
hasInformalUsage
chosen
Indicates that something is used in casual or non-standard contexts rather than in formal or official usage.
-
D.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
-
E.
mayExpress
Indicates that an entity is permitted or allowed to express, convey, or articulate something (such as an idea, emotion, or statement) in a given context.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 9:06 p.m.