Triple
T29734023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wonsu of the Republic |
E752405
|
entity |
| Predicate | NATORankCodeApproximation |
P24247
|
FINISHED |
| Object | OF-10 |
—
|
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: OF-10 | Statement: [Wonsu of the Republic, NATORankCodeApproximation, OF-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATORankCodeApproximation Context triple: [Wonsu of the Republic, NATORankCodeApproximation, OF-10]
-
A.
NATORankCode
chosen
Indicates the standardized NATO rank classification assigned to a military person or position within the alliance.
-
B.
portRank
Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
-
C.
nationalRankingScope
Indicates that the ranking being referred to is evaluated at the national (country-wide) level rather than regional or local scopes.
-
D.
nationalRank
Indicates the position or standing of an entity within a ranking system at the national level.
-
E.
addressesRank
Indicates that one entity directs communication, content, or behavior toward another entity based on that entity’s rank or hierarchical status.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67332b6808190bb4948d78da1e440 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:44 p.m.