Triple
T5604850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honor et Amor |
E147207
|
entity |
| Predicate | denotesConcept |
P531
|
FINISHED |
| Object | family honor |
—
|
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: family honor | Statement: [Honor et Amor, denotesConcept, family honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesConcept Context triple: [Honor et Amor, denotesConcept, family honor]
-
A.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
categoryConcept
Indicates that one entity serves as a categorical type or conceptual class under which the other entity is grouped or classified.
-
C.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
E.
addressesConcept
Indicates that one entity deals with, discusses, or responds to the subject matter represented by 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020f9408481908cf006074c726301 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.