Triple
T35805181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JBL |
E1035084
|
entity |
| Predicate | signatureGimmick |
P51216
|
FINISHED |
| Object | wealthy Wall Street-style tycoon |
—
|
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: wealthy Wall Street-style tycoon | Statement: [JBL, signatureGimmick, wealthy Wall Street-style tycoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureGimmick Context triple: [JBL, signatureGimmick, wealthy Wall Street-style tycoon]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signatureFeature
chosen
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
C.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
signatureNumber
Indicates the identifying number assigned to a specific signature within a document or signing process.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.