Triple
T2159763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run the World (Girls) |
E47972
|
entity |
| Predicate | signatureChant |
P15355
|
FINISHED |
| Object | Who run the world? Girls! |
—
|
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: Who run the world? Girls! | Statement: [Run the World (Girls), signatureChant, Who run the world? Girls!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureChant Context triple: [Run the World (Girls), signatureChant, Who run the world? Girls!]
-
A.
signature
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signatureSound
Indicates that something has a distinctive, characteristic sound that uniquely identifies it.
-
C.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
D.
signatureLine
Indicates that an entity serves as a designated place or line where a signature is written or recorded.
-
E.
signatureWork
Indicates that the work is a defining or most representative creation associated with an entity (such as a person, group, or organization).
- 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8894d481908eda9363fd36fea6 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.