Triple
T36505040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colodon |
E899437
|
entity |
| Predicate | hasDigitConfiguration |
P199865
|
FINISHED |
| Object | odd-toed |
—
|
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: odd-toed | Statement: [Colodon, hasDigitConfiguration, odd-toed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitConfiguration Context triple: [Colodon, hasDigitConfiguration, odd-toed]
-
A.
hasDigitSet
Indicates that an entity is associated with a specific set or collection of digits.
-
B.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
C.
hasRoutingCodeDigit
Indicates that an entity’s routing code contains a specific digit at a particular position or as part of its structure.
-
D.
digitType
Indicates the specific category or kind of digit (such as numerical, symbolic, or positional type) associated with an entity.
-
E.
hasDigitalControl
Indicates that one entity possesses the authority or capability to manage, configure, or operate another entity through digital or electronic means.
- F. None of above. chosen
Provenance (4 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:10 p.m.