Triple
T26756431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franz Sanchez |
E674681
|
entity |
| Predicate | usesAsFront |
P109848
|
FINISHED |
| Object | Isthmus City bank |
—
|
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: Isthmus City bank | Statement: [Franz Sanchez, usesAsFront, Isthmus City bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsFront Context triple: [Franz Sanchez, usesAsFront, Isthmus City bank]
-
A.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
B.
usesBaseFront
Indicates that an entity performs an action or operates while oriented toward or relying on its front-facing base as the primary point of use or support.
-
C.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
frontsOfUse
Indicates that something serves as the primary face, interface, or outward-facing side through which another thing is accessed, used, or interacted with.
-
E.
frontsUsedOn
chosen
Indicates that one entity uses or employs the front side or front-facing part of another entity.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 3:56 a.m.