Triple
T30079819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Femme Fatale Tour |
E764420
|
entity |
| Predicate | includesProps |
P46693
|
FINISHED |
| Object | multi-level stage |
—
|
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: multi-level stage | Statement: [Femme Fatale Tour, includesProps, multi-level stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProps Context triple: [Femme Fatale Tour, includesProps, multi-level stage]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
usesProp
chosen
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
C.
includesMap
Indicates that one entity contains or incorporates another entity in the form of a map or mapping structure.
-
D.
selectionIncludes
Indicates that a chosen set or subset explicitly contains or covers the specified element(s) as part of the selection.
-
E.
includesProvider
Indicates that one entity contains or encompasses another entity that serves as a provider within its scope or structure.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: April 29, 2026, 7:02 p.m.