Triple
T26437350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coining the "Pine Tree Shilling" |
E664986
|
entity |
| Predicate | hasProfessionOfMainActor |
P110410
|
FINISHED |
| Object | silversmith |
—
|
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: silversmith | Statement: [Coining the "Pine Tree Shilling", hasProfessionOfMainActor, silversmith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProfessionOfMainActor Context triple: [Coining the "Pine Tree Shilling", hasProfessionOfMainActor, silversmith]
-
A.
mainProfessionOfDirector
Indicates the primary professional occupation or field in which a given director mainly works.
-
B.
hasCoProtagonistOccupation
Indicates that two or more co-protagonists share a specified occupation or professional role.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
actorNotableOccupation
Indicates that a person (typically an actor) is associated with a particular occupation or professional role for which they are especially well known.
-
E.
leadActorOccupation
chosen
Indicates that the occupation specified is the primary professional role of the lead actor in a given work or context.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 26, 2026, 11:55 p.m.