Triple
T28374261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 商汤 |
E718713
|
entity |
| Predicate | 历史记载来源 |
P150962
|
FINISHED |
| Object | 史记 |
—
|
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: 史记 | Statement: [商汤, 历史记载来源, 史记]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 历史记载来源 Context triple: [商汤, 历史记载来源, 史记]
-
A.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
B.
namedInHistoricalSources
chosen
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
C.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
D.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
E.
historicalResource
Indicates that a resource has historical significance or relevance, typically documenting or representing past events, conditions, or contexts.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5d1290819087cbb832239699d4 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:02 a.m.