Triple
T6173418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maran |
E137758
|
entity |
| Predicate | honorificFunction |
P69223
|
FINISHED |
| Object | express reverence |
—
|
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: express reverence | Statement: [Maran, honorificFunction, express reverence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificFunction Context triple: [Maran, honorificFunction, express reverence]
-
A.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
B.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
C.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
D.
honorificNameOf
Indicates that one entity is the honorific or respectful name or title used to refer to another entity.
-
E.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.