Triple
T17557540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOML |
E427624
|
entity |
| Predicate | keyValueSeparator |
P86777
|
FINISHED |
| Object | = |
—
|
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: = | Statement: [TOML, keyValueSeparator, =]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyValueSeparator Context triple: [TOML, keyValueSeparator, =]
-
A.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
B.
separators
chosen
Indicates that one entity divides, distinguishes, or creates a boundary between two or more other entities.
-
C.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
separatesAt
Indicates that one entity divides or splits another entity into distinct parts at a specific point, boundary, or location.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562413d08190acaa5272046d3626 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.