Triple
T23588705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creative Data Lions |
E582415
|
entity |
| Predicate | eligibleEntrants |
P98750
|
FINISHED |
| Object | agencies |
—
|
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: agencies | Statement: [Creative Data Lions, eligibleEntrants, agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleEntrants Context triple: [Creative Data Lions, eligibleEntrants, agencies]
-
A.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
B.
eligibleIn
chosen
Indicates that an entity meets the necessary conditions or criteria to qualify for participation, use, or consideration within a specified context, domain, or scope.
-
C.
eligiblePersons
Indicates that certain persons meet the required conditions or criteria to qualify for a particular status, benefit, or participation.
-
D.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0336aec8190856aee4a8273c3e5 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.