Triple
T30155445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 航运等级 |
P168499
|
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: [长江, 航运等级, 世界重要内河航道之一]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 航运等级 Context triple: [长江, 航运等级, 世界重要内河航道之一]
-
A.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
B.
navalHierarchyLevel
Indicates the relative rank or position of an entity within a naval command or organizational hierarchy.
-
C.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
D.
shipFlag
Indicates that a ship is registered under and legally operates under the authority of a specified national flag or registry.
-
E.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.