Triple
T34258195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP |
E878950
|
entity |
| Predicate | firstLetterOrigin |
P3818
|
FINISHED |
| Object | S from São |
—
|
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: S from São | Statement: [SP, firstLetterOrigin, S from São]
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 (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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.