Triple
T25310467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUF |
E634593
|
entity |
| Predicate | typicalSymbolSpacing |
P95533
|
FINISHED |
| Object | non‑breaking space before Ft |
—
|
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: non‑breaking space before Ft | Statement: [HUF, typicalSymbolSpacing, non‑breaking space before Ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSymbolSpacing Context triple: [HUF, typicalSymbolSpacing, non‑breaking space before Ft]
-
A.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
B.
hasAlternativeSpacing
chosen
Indicates that an entity is associated with one or more alternative ways of spacing its characters or components compared to a primary or standard form.
-
C.
typicalPadding
Indicates that one entity specifies the standard or commonly used amount of padding applied to another entity.
-
D.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
E.
hasMeanSpacing
Indicates the average distance or interval between repeated or adjacent elements in a pattern, structure, or arrangement.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 21, 2026, 1:26 p.m.