Triple
T38086414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anping Fort |
E950986
|
entity |
| Predicate | operatorAfter1662 |
P204184
|
FINISHED |
| Object | Kingdom of Tungning |
E282323
|
NE 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: Kingdom of Tungning | Statement: [Anping Fort, operatorAfter1662, Kingdom of Tungning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAfter1662 Context triple: [Anping Fort, operatorAfter1662, Kingdom of Tungning]
-
A.
operatorAfter1898
Indicates that the entity served as an operator of the related entity at some point after the year 1898.
-
B.
operatorLater
Indicates that one operator or operation occurs at a later time than another in a temporal ordering.
-
C.
operatedAfter
Indicates that one operation or action occurred later in time than another specified operation or action.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
operatorAfterConsolidation
Indicates that one operator entity succeeds or replaces another operator entity after a consolidation event (such as a merger or acquisition).
- F. None of above. chosen
Provenance (5 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4193b3907881908ff7ba8e3596aff4 |
completed | June 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_6a03446d9d988190981f245d74c3444b |
completed | May 12, 2026, 3:17 p.m. |
Created at: May 3, 2026, 4:21 p.m.