Triple
T38612993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby (British rhyming slang) |
E934529
|
entity |
| Predicate | oftenUsedInPhrase |
P79823
|
FINISHED |
| Object | have a Ruby |
—
|
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: have a Ruby | Statement: [Ruby (British rhyming slang), oftenUsedInPhrase, have a Ruby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenUsedInPhrase Context triple: [Ruby (British rhyming slang), oftenUsedInPhrase, have a Ruby]
-
A.
isUsedInPhrase
chosen
Indicates that something (such as a word, expression, or symbol) appears as a component within a particular phrase.
-
B.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
C.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
D.
oftenUsedAfter
Indicates that one entity is frequently or typically used immediately following another entity in a sequence or workflow.
-
E.
usedInOrAround
Indicates that something is utilized, applied, or occurs within the context of, or in the immediate vicinity of, something else.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:32 p.m.