Triple
T33029007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | comp.lang.c |
E845113
|
entity |
| Predicate | hasFAQ |
P193553
|
FINISHED |
| Object | comp.lang.c FAQ |
—
|
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: comp.lang.c FAQ | Statement: [comp.lang.c, hasFAQ, comp.lang.c FAQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFAQ Context triple: [comp.lang.c, hasFAQ, comp.lang.c FAQ]
-
A.
hasKeyQuestion
Indicates that one entity possesses or is associated with a primary or central question relevant to another entity.
-
B.
canAnswerQuestionsIn
Indicates that an entity has the ability to answer questions within a specified context, domain, or environment.
-
C.
hasClarificationsBy
Indicates that one entity provides additional explanations, details, or disambiguation for another entity.
-
D.
canAnswerQuestions
Indicates that an entity has the ability or capacity to respond correctly or appropriately to questions.
-
E.
canAsk
Indicates that one entity has the ability or permission to pose a question or make a request to another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 1, 2026, 1:24 a.m.