Triple
T34833255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Paulista |
E1004122
|
entity |
| Predicate | hasAlternativeDesignationOf |
P48076
|
FINISHED |
| Object | Sorocaba, São Paulo |
—
|
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: Sorocaba, São Paulo | Statement: [Manchester Paulista, hasAlternativeDesignationOf, Sorocaba, São Paulo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeDesignationOf Context triple: [Manchester Paulista, hasAlternativeDesignationOf, Sorocaba, São Paulo]
-
A.
alternateDesignation
chosen
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
-
B.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
C.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
D.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
E.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4 p.m.