Triple
T27114302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joanne |
E686797
|
entity |
| Predicate | hasSignatureNumber |
P147159
|
FINISHED |
| Object | The Ladies Who Lunch |
—
|
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: The Ladies Who Lunch | Statement: [Joanne, hasSignatureNumber, The Ladies Who Lunch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignatureNumber Context triple: [Joanne, hasSignatureNumber, The Ladies Who Lunch]
-
A.
isSignatureNumberOf
Indicates that a number serves as the unique signature or identifying code associated with a particular entity.
-
B.
signatureNumber
chosen
Indicates the identifying number assigned to a specific signature within a document or signing process.
-
C.
hasSignatureUse
Indicates that an entity is used as an official or primary signature or identifying mark for another entity.
-
D.
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.
-
E.
hasSignatureUser
Indicates that a particular user is designated as the signer or signature owner associated with an entity or record.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 8:55 a.m.