Triple
T31366429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matmos |
E800020
|
entity |
| Predicate | formerlyBasedIn |
P4907
|
FINISHED |
| Object | San Francisco |
—
|
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: San Francisco | Statement: [Matmos, formerlyBasedIn, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyBasedIn Context triple: [Matmos, formerlyBasedIn, San Francisco]
-
A.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
B.
formerResidenceOf
chosen
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
C.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
D.
formerlyInDistrict
Indicates that an entity was once located in or part of a particular district, but is no longer within that district.
-
E.
residedOn
Indicates that an entity lived or had its primary dwelling at a specific location during a certain period.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: April 29, 2026, 9:18 p.m.