Triple
T37409679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jun-fan |
E929526
|
entity |
| Predicate | hasBearerBirthPlace |
P1
|
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: [Jun-fan, hasBearerBirthPlace, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBearerBirthPlace Context triple: [Jun-fan, hasBearerBirthPlace, San Francisco]
-
A.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
B.
containsBirthplaceTown
Indicates that one entity includes or specifies the town where another entity was born.
-
C.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
-
D.
placeOfBirth
chosen
Indicates the location where a person or other entity was born.
-
E.
titleHolderBirthTerritory
Indicates the territory in which the holder of a title was born.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:16 p.m.