Triple
T10316801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Geological Survey hydrologic unit codes |
E242036
|
entity |
| Predicate | maximumCodeLength |
P56985
|
FINISHED |
| Object | 12 digits |
—
|
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: 12 digits | Statement: [United States Geological Survey hydrologic unit codes, maximumCodeLength, 12 digits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCodeLength Context triple: [United States Geological Survey hydrologic unit codes, maximumCodeLength, 12 digits]
-
A.
maximumCodePoints
Indicates the maximum number of Unicode code points that are allowed or supported in a given context or value.
-
B.
maxBytesPerCodePoint
Indicates the maximum number of bytes used to encode a single code point in a given character encoding or data representation.
-
C.
scriptCodeLength
Indicates the length or number of characters in a given script or code sequence.
-
D.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
E.
hasMaximumLength
chosen
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.