Triple
T28323631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tang Shu Yu |
E717347
|
entity |
| Predicate | enfeoffedIn |
P117346
|
FINISHED |
| Object | Tang (唐) |
—
|
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: Tang (唐) | Statement: [Tang Shu Yu, enfeoffedIn, Tang (唐)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enfeoffedIn Context triple: [Tang Shu Yu, enfeoffedIn, Tang (唐)]
-
A.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
B.
heldFief
chosen
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
C.
formerFiefOf
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
-
D.
associatedWithFeudalOffice
Indicates a relationship where an entity is linked to, holds, or is otherwise connected with a specific feudal office or position within a feudal system.
-
E.
typeOfFeudalGrant
Indicates the specific kind or category of feudal grant that characterizes the relationship between a grantor and a grantee within a feudal system.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492ce1ec81908f51388ed8eea019 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:26 a.m.