Triple
T34258195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP |
E878950
|
entity |
| Predicate | firstLetterOrigin |
—
|
GENERATED |
| Object | S from São |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLetterOrigin Context triple: [SP, firstLetterOrigin, S from São]
-
A.
firstLetter
chosen
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
B.
secondLetterOrigin
Indicates that the second letter of one entity’s name or identifier originates from, or is derived based on, another entity.
-
C.
introducedAsLetter
Indicates that one entity is presented or identified in the form of a written letter to another entity.
-
D.
nameLetter
Indicates that a specific letter is part of, or occurs within, an entity’s name.
-
E.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
- F. None of above.
Provenance (1 batch)
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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.