Triple
T3318549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian alphabet |
E69737
|
entity |
| Predicate | originalNumberOfLetters |
P3567
|
FINISHED |
| Object | 36 |
—
|
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: 36 | Statement: [Armenian alphabet, originalNumberOfLetters, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNumberOfLetters Context triple: [Armenian alphabet, originalNumberOfLetters, 36]
-
A.
hasNumberOfLetters
Indicates a relationship where an entity is associated with the count of letters it contains.
-
B.
hasApproximateNumberOfLetters
Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
-
C.
hasLetterCount
chosen
Indicates that an entity is associated with a specific number representing how many letters it contains.
-
D.
originalNumberOfLanguages
Indicates the initial count of distinct languages associated with an entity before any changes or reductions occur.
-
E.
originalNumberOfMembers
Indicates the initial total count of members in a group or organization before any changes such as additions or removals.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1151f3c8190911af4edac701116 |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.