Triple
T27560034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub Flavored Markdown |
E695745
|
entity |
| Predicate | supportsTaskListSyntax |
P198484
|
FINISHED |
| Object | [ ] and [x] in list items |
—
|
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: [ ] and [x] in list items | Statement: [GitHub Flavored Markdown, supportsTaskListSyntax, [ ] and [x] in list items]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTaskListSyntax Context triple: [GitHub Flavored Markdown, supportsTaskListSyntax, [ ] and [x] in list items]
-
A.
canBeTaskOrganizedWith
Indicates that one entity can be grouped, scheduled, or managed together with another as part of the same task or workflow.
-
B.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
C.
multitaskingSupport
Indicates that an entity is capable of performing multiple tasks or operations concurrently or in parallel.
-
D.
Tasking Manager
Indicates a relationship where one entity assigns, organizes, or oversees tasks or work items for others to perform.
-
E.
hasTaskGroup
Indicates that an entity is associated with, or belongs to, a specific task group that organizes or groups related tasks.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69feecf102e08190b237c29e45beeca0 |
completed | May 9, 2026, 8:14 a.m. |
Created at: April 27, 2026, 1:38 p.m.