Triple
T17775454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hsia-men |
E443754
|
entity |
| Predicate | functionOfName |
P34236
|
FINISHED |
| Object | identification of a major Chinese port |
—
|
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: identification of a major Chinese port | Statement: [Hsia-men, functionOfName, identification of a major Chinese port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionOfName Context triple: [Hsia-men, functionOfName, identification of a major Chinese port]
-
A.
functionInName
chosen
Indicates that the name of one entity includes or references the function or role of another entity.
-
B.
namingFunction
Indicates a relationship where one entity serves as the name or naming mechanism assigned to another entity.
-
C.
nameOf
Indicates that one entity is the name or designation of another entity.
-
D.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
E.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871c23408190aae7f1a2c77a10cb |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.