Triple
T31191462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How Do You Do It? |
E795191
|
entity |
| Predicate | wasOfferedTo |
P129222
|
FINISHED |
| Object | The Beatles |
—
|
NE NERFINISHED |
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: The Beatles | Statement: [How Do You Do It?, wasOfferedTo, The Beatles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOfferedTo Context triple: [How Do You Do It?, wasOfferedTo, The Beatles]
-
A.
offeredOver
chosen
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
B.
firstOffered
Indicates that one entity was the earliest or initial provider or proposer of something to another entity or context.
-
C.
offeredRewardTo
Indicates that one entity has proposed or promised a reward to another entity, typically as an incentive for a specific action or outcome.
-
D.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
E.
usedAsOfferingAt
Indicates that something is employed or presented as an offering in a particular context, place, or event.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:08 p.m.