Triple
T26581050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor David Brenner |
E667076
|
entity |
| Predicate | signatureUsedOn |
P150
|
FINISHED |
| Object | 1909 Lincoln cent |
—
|
NE NERFINISHED |
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: 1909 Lincoln cent | Statement: [Victor David Brenner, signatureUsedOn, 1909 Lincoln cent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureUsedOn Context triple: [Victor David Brenner, signatureUsedOn, 1909 Lincoln cent]
-
A.
hasSignatureUse
Indicates that an entity is used as an official or primary signature or identifying mark for another entity.
-
B.
signatureEventOf
Indicates that a given event represents or records the signing (or creation) of the associated entity, such as a document, agreement, or artifact.
-
C.
signature
chosen
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
D.
signedBefore
Indicates that one signing event occurred earlier in time than another signing event.
-
E.
signatureConcept
Indicates that one concept is the defining or characteristic idea that most distinctly represents or identifies another concept.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:03 a.m.