Triple
T21067769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop on Pop |
E519020
|
entity |
| Predicate | usesVocabulary |
P18536
|
FINISHED |
| Object | short phonetic words |
—
|
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: short phonetic words | Statement: [Hop on Pop, usesVocabulary, short phonetic words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVocabulary Context triple: [Hop on Pop, usesVocabulary, short phonetic words]
-
A.
hasVocabularyFrom
Indicates that one entity’s vocabulary, terminology, or set of terms is derived from, based on, or taken from another entity.
-
B.
usesControlledVocabulary
Indicates that one entity selects terms or values from a predefined, standardized set rather than using free-form or arbitrary expressions.
-
C.
usesTerminologyFrom
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
D.
hasKnownVocabulary
chosen
Indicates that an entity possesses a defined, identifiable set of terms or words that it can recognize or use.
-
E.
hasDistinctVocabulary
Indicates that one entity’s vocabulary is different or distinguishable from that of another 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb5772481909e32af3b3a69df76 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:45 p.m.