Triple
T17519935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | full-stack-fastapi-template |
E426656
|
entity |
| Predicate | taskQueueComponent |
P79890
|
FINISHED |
| Object | Celery workers |
—
|
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: Celery workers | Statement: [full-stack-fastapi-template, taskQueueComponent, Celery workers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskQueueComponent Context triple: [full-stack-fastapi-template, taskQueueComponent, Celery workers]
-
A.
usesQueue
chosen
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
B.
taskForce
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
C.
taskDomain
Indicates that a task belongs to, is categorized under, or is associated with a particular domain or area of activity.
-
D.
taskingSource
Indicates the entity that assigns, initiates, or is responsible for requesting a particular task or activity for another entity.
-
E.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.