Triple
T24417151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Rei do Futebol |
E615615
|
entity |
| Predicate | appliedAfter |
P67762
|
FINISHED |
| Object | Pelé’s retirement |
—
|
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: Pelé’s retirement | Statement: [O Rei do Futebol, appliedAfter, Pelé’s retirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAfter Context triple: [O Rei do Futebol, appliedAfter, Pelé’s retirement]
-
A.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
B.
appliesToAfter
chosen
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
-
C.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
-
D.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
E.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958645248190a22bd0b8bcc2dfe2 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.