Triple
T25231928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagoda (gold coin) |
E632238
|
entity |
| Predicate | valueRank |
P152574
|
FINISHED |
| Object | high-value coin |
—
|
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: high-value coin | Statement: [Pagoda (gold coin), valueRank, high-value coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRank Context triple: [Pagoda (gold coin), valueRank, high-value coin]
-
A.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
C.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
capacityRank
Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df5eafc819089a2735bd8177a27 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:06 p.m.