Triple
T30481153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guo Zongxun |
E775589
|
entity |
| Predicate | nativeScriptName |
P169780
|
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: [Guo Zongxun, nativeScriptName, 郭宗訓]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeScriptName Context triple: [Guo Zongxun, nativeScriptName, 郭宗訓]
-
A.
nativeApplication
Indicates that an application is specifically designed to run directly on a particular platform or operating system, using its native runtime and capabilities.
-
B.
nativeTitleOutcome
Indicates the result or status achieved in relation to a native or original title (such as a formal designation, rank, or work title) following some process or event.
-
C.
runtimeName
Indicates the name of the runtime environment or platform under which an entity (such as a program or process) is executed.
-
D.
nativeTitleDeterminationType
Indicates the method or criteria used to determine an entity’s original or native title.
-
E.
nativeTitleDeterminationArea
Indicates the geographic area within which a native title claim or determination is legally recognized or assessed.
- F. None of above. chosen
Provenance (4 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687415610819081818d08f7c79a81 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:12 p.m.