Triple
T32060471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Seminar |
E818733
|
entity |
| Predicate | badgeRequirement |
P173799
|
FINISHED |
| Object | spark completion |
—
|
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: spark completion | Statement: [You Seminar, badgeRequirement, spark completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeRequirement Context triple: [You Seminar, badgeRequirement, spark completion]
-
A.
boardingRequirement
Indicates the conditions or criteria that must be met for an entity to be allowed to board another entity (such as a vehicle, vessel, or aircraft).
-
B.
campaignRequirement
Indicates that one entity specifies a condition or prerequisite that must be met for a campaign associated with another entity.
-
C.
noticeRequirement
Indicates that one party is obligated to provide advance notification to another party before a specified action, change, or event occurs.
-
D.
activationRequirement
Indicates the conditions or prerequisites that must be satisfied for an entity, process, or function to become active or operational.
-
E.
trialRequirement
Indicates that a certain condition, action, or resource is required for a trial to be conducted or considered valid.
- F. None of above. chosen
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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:21 a.m.