Triple
T8545341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Beautiful Child |
E202306
|
entity |
| Predicate | hasAuthorialSignature |
P54115
|
FINISHED |
| Object | Truman Capote’s lyrical style |
—
|
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: Truman Capote’s lyrical style | Statement: [A Beautiful Child, hasAuthorialSignature, Truman Capote’s lyrical style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialSignature Context triple: [A Beautiful Child, hasAuthorialSignature, Truman Capote’s lyrical style]
-
A.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
B.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
-
C.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
D.
hasSignatureConcept
chosen
Indicates that something is associated with or characterized by a defining concept that uniquely represents its core meaning or identity.
-
E.
hasAuthor
Indicates that an entity is written or created by a specific author.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe74f62148190bfd6cacf5d4f74b6 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.