Triple
T35208097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Time Becks |
E1016593
|
entity |
| Predicate | associatedWithMoniker |
P24023
|
FINISHED |
| Object | The Man |
E1016592
|
NE 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: The Man | Statement: [Big Time Becks, associatedWithMoniker, The Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMoniker Context triple: [Big Time Becks, associatedWithMoniker, The Man]
-
A.
associatedName
chosen
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
C.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
associatedWithMonster
Indicates a relationship in which an entity is connected or linked in some notable way to a monster.
- F. None of above.
Provenance (4 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a1969d88190a9e4d62046c9d62b |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.