Triple
T5803612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Players Inc. |
E128686
|
entity |
| Predicate | managesRightsFor |
P39434
|
FINISHED |
| Object | NFL players’ names |
—
|
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: NFL players’ names | Statement: [NFL Players Inc., managesRightsFor, NFL players’ names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesRightsFor Context triple: [NFL Players Inc., managesRightsFor, NFL players’ names]
-
A.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
B.
establishesRight
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
C.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
D.
ownsOrManages
Indicates that one entity has ownership of, or managerial control over, another entity.
-
E.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.