Triple
T36844433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyresö FF |
E910501
|
entity |
| Predicate | employedPlayer |
P83995
|
FINISHED |
| Object | Marta |
—
|
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: Marta | Statement: [Tyresö FF, employedPlayer, Marta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedPlayer Context triple: [Tyresö FF, employedPlayer, Marta]
-
A.
employedActor
Indicates that one entity has hired or currently employs another entity to perform work or services.
-
B.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
C.
employedTo
chosen
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
D.
employedUnder
Indicates that one entity works as an employee under the authority, supervision, or organizational structure of another entity.
-
E.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:13 p.m.