Triple
T37632615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfect Plex (as tribute) |
E936392
|
entity |
| Predicate | pinningCombination |
P188543
|
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: [Perfect Plex (as tribute), pinningCombination, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pinningCombination Context triple: [Perfect Plex (as tribute), pinningCombination, yes]
-
A.
originalCombinationFor
Indicates that one entity is the initial or source combination from which another combined entity is derived or constructed.
-
B.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
C.
needleArrangement
Indicates how needles are positioned or organized relative to each other in a given context.
-
D.
typicalCombinationWith
Indicates that one entity is commonly or characteristically used, found, or occurs together in combination with another entity.
-
E.
isConsideredCombinationOf
Indicates that something is regarded as being formed by or equivalent to a specific combination of other things or components.
- F. None of above. chosen
Provenance (4 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.