Triple
T16919112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 排云殿 |
E410395
|
entity |
| Predicate | 所有权 |
P7585
|
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.
ownershipType
chosen
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
B.
ownershipRecord
Indicates that there exists a documented relationship specifying which entity legally owns or possesses another entity, typically including details such as owner, owned item, and relevant terms or period of ownership.
-
C.
ownershipEnd
Indicates the point or event at which an entity’s ownership of another entity ceases or is terminated.
-
D.
ownershipCharacteristic
Indicates that one entity possesses a particular quality, attribute, or condition specifically in its role as an owner of another entity.
-
E.
ownershipStart
Indicates the point in time at which an entity begins to own or hold legal possession of another 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdec3d0c8190994a0fca335c65d6 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.