Triple
T19872436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 洛河 |
E477550
|
entity |
| Predicate | 考古意义 |
P12027
|
FINISHED |
| Object | 流域内分布有多处史前文化遗址 |
—
|
LITERAL FINISHED |
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.
hasArchaeologicalValue
chosen
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
B.
loreSignificance
Indicates that something holds notable importance, relevance, or impact within a fictional world’s backstory, mythology, or overarching narrative.
-
C.
anthropologicalSignificance
Indicates that something holds importance or value for understanding human cultures, societies, or behaviors from an anthropological perspective.
-
D.
hasArtHistoricalSignificance
Indicates that something holds notable importance or influence within the context of art history.
-
E.
historicSignificanceScope
Indicates the extent or level (e.g., local, national, global) at which something is considered historically significant.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d826f88190be04188997952d1b |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.