Triple
T10753210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TURKISH |
E253622
|
entity |
| Predicate | callSignFormatExample |
P95036
|
FINISHED |
| Object | TURKISH one two three |
—
|
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: TURKISH one two three | Statement: [TURKISH, callSignFormatExample, TURKISH one two three]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignFormatExample Context triple: [TURKISH, callSignFormatExample, TURKISH one two three]
-
A.
callSignSpokenForm
Indicates the spoken or verbalized form used to refer to a particular call sign.
-
B.
callSignNumber
Indicates the specific identifying number assigned as a call sign to an entity for communication or identification purposes.
-
C.
associatedWithCallSignFormat
chosen
Indicates a relationship where something is linked to, or uses, a particular call sign format.
-
D.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
E.
callSignForPerson
Indicates that a particular call sign is assigned to or used by a specific person.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dc2543c8190bb060aa7a1fed6a6 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.