Triple
T36185304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaifeng synagogue |
E1046827
|
entity |
| Predicate | earliestCommunityEvidence |
P113262
|
FINISHED |
| Object | Northern Song dynasty |
—
|
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: Northern Song dynasty | Statement: [Kaifeng synagogue, earliestCommunityEvidence, Northern Song dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestCommunityEvidence Context triple: [Kaifeng synagogue, earliestCommunityEvidence, Northern Song dynasty]
-
A.
earliestEvidenceSite
Indicates that the related site is the location where the earliest known evidence of the subject was found.
-
B.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
-
C.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
D.
earliestFindsDateTo
Indicates the earliest known date at which the finding, discovery, or observation of one entity is recorded as relating to another entity.
-
E.
earliestWellKnownExample
Indicates that one entity is the earliest well-known example or instance of the other entity.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:08 p.m.