Triple
T14069613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tengwang Pavilion |
E338569
|
entity |
| Predicate | originallyBuiltIn |
P13567
|
FINISHED |
| Object | 653 |
—
|
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: 653 | Statement: [Tengwang Pavilion, originallyBuiltIn, 653]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyBuiltIn Context triple: [Tengwang Pavilion, originallyBuiltIn, 653]
-
A.
builtIn
Indicates that one entity is inherently included as a standard, pre-existing component or feature of another entity, rather than being added or installed separately.
-
B.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
C.
originallyBuiltUnder
Indicates that something was first constructed during the rule, authority, or administration of a particular person, group, or regime.
-
D.
originallyBuiltBy
chosen
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568d0404819087e0fe37c72162cb |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.