Triple
T27586358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellowdog Updater |
E699697
|
entity |
| Predicate | sharesConceptsWith |
P40775
|
FINISHED |
| Object | YUM |
—
|
NE NERFINISHED |
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: YUM | Statement: [Yellowdog Updater, sharesConceptsWith, YUM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesConceptsWith Context triple: [Yellowdog Updater, sharesConceptsWith, YUM]
-
A.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
B.
sharesComplexWith
Indicates that two entities are components of, or co-residents within, the same larger complex or composite structure.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesNotableAssociationWith
Indicates a mutual, noteworthy connection or linkage between two entities that is significant enough to be recognized or highlighted.
-
E.
sharesElementsWith
chosen
Indicates that two entities have one or more elements or components in common.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 27, 2026, 2:04 p.m.