Triple
T23045840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA Female Player of the Century (co-winner) |
E573874
|
entity |
| Predicate | hasNumberOfRecipients |
P7074
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [FIFA Female Player of the Century (co-winner), hasNumberOfRecipients, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfRecipients Context triple: [FIFA Female Player of the Century (co-winner), hasNumberOfRecipients, 2]
-
A.
hasFirstRecipient
Indicates that an entity is the initial or primary recipient of something (such as a message, award, or transfer) in a sequence or set of recipients.
-
B.
hasRecipientField
Indicates that something includes or defines a field intended to specify a recipient.
-
C.
totalRecipients
chosen
Indicates the total number of distinct entities that receive something in the context of the described relationship or action.
-
D.
hasRecipientRole
Indicates that a specified entity serves as the recipient or target role in a given interaction, transaction, or relationship.
-
E.
hasRecipientWork
Indicates that a work (such as a document, message, or creative piece) is directed or assigned to a specific recipient entity.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185192754819093a87d23371e7bbc |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.