Triple
T4522049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justified and Stripped Tour |
E103289
|
entity |
| Predicate | featuresSoloSets |
P57211
|
FINISHED |
| Object | Justin Timberlake solo set |
—
|
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: Justin Timberlake solo set | Statement: [Justified and Stripped Tour, featuresSoloSets, Justin Timberlake solo set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSoloSets Context triple: [Justified and Stripped Tour, featuresSoloSets, Justin Timberlake solo set]
-
A.
setsIn
Indicates that one entity places or positions another entity into or within a specified container, location, or context.
-
B.
featureSet
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
C.
sets
Indicates that an entity places, positions, or puts another entity into a particular state, location, or configuration.
-
D.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
-
E.
sharesSetsWith
Indicates that two entities have one or more sets in common, or participate in at least one identical set.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574bd6908190b939d92b5809b101 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.