Triple
T11494013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via |
E272487
|
entity |
| Predicate | typicalLengthInLetters |
P76555
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Via, typicalLengthInLetters, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLengthInLetters Context triple: [Via, typicalLengthInLetters, 3]
-
A.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
B.
typicalNameLength
chosen
Indicates the usual or characteristic number of characters in the names of entities in a given context.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
hasApproximateNumberOfLetters
Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
-
E.
hasNumberOfLetters
Indicates a relationship where an entity is associated with the count of letters it contains.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85ddffdf88190a00e94ad5b8b91a5 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.