Triple
T17360039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carricart |
E422043
|
entity |
| Predicate | isOrthographicVariantPossible |
P33995
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Carricart, isOrthographicVariantPossible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrthographicVariantPossible Context triple: [Carricart, isOrthographicVariantPossible, yes]
-
A.
orthographicVariant
chosen
Indicates that two written forms are different spellings or orthographic representations of the same linguistic item.
-
B.
hasOrthographicPreference
Indicates that one entity prefers or selects a particular written or spelling form of another entity.
-
C.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
D.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
E.
orthographicProperty
Indicates a relationship where a specific written or spelling-related characteristic is attributed to or associated with an entity.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4cacd881909fd722068b019f25 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.