Triple
T28075858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langya Commandery |
E709539
|
entity |
| Predicate | historicallyNotableDuring |
P8452
|
FINISHED |
| Object | Han dynasty |
—
|
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: Han dynasty | Statement: [Langya Commandery, historicallyNotableDuring, Han dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyNotableDuring Context triple: [Langya Commandery, historicallyNotableDuring, Han dynasty]
-
A.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
B.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
C.
hasHistoricalSignificanceThrough
Indicates that one entity possesses historical importance or relevance by means of, or as established through, its connection or association with another entity or event.
-
D.
chronologicallyNotableEvent
Indicates that an event is significant or noteworthy in terms of its position or impact within a chronological sequence of events.
-
E.
notableDuring
chosen
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: April 27, 2026, 8:48 p.m.