Triple
T31992229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 延 |
E816901
|
entity |
| Predicate | hasFourCornerCode |
P52964
|
FINISHED |
| Object | 1722 |
—
|
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: 1722 | Statement: [延, hasFourCornerCode, 1722]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFourCornerCode Context triple: [延, hasFourCornerCode, 1722]
-
A.
fourCornerCode
chosen
Indicates a standardized four-character code used to classify or identify something based on its four key components or positions.
-
B.
hasFourLetterCode
Indicates that an entity is associated with a code consisting of exactly four characters.
-
C.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
D.
hasCornerCount
Indicates that an entity is associated with a specific number of corners.
-
E.
hasFourthCharacter
Indicates that one entity possesses or is associated with a specific fourth character in a sequence or string.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.