Triple
T29799091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Greatest |
E756640
|
entity |
| Predicate | selfAppliedBy |
P4794
|
FINISHED |
| Object | Muhammad Ali |
—
|
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: Muhammad Ali | Statement: [The Greatest, selfAppliedBy, Muhammad Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfAppliedBy Context triple: [The Greatest, selfAppliedBy, Muhammad Ali]
-
A.
appliedBy
chosen
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
appliedBecauseOf
Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
-
E.
isAppliedBeyond
Indicates that something (such as a rule, method, or effect) is used or has influence outside its original or primary scope, context, or boundary.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e861f08190a85ab46799e50c74 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:17 p.m.