Triple
T5430245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evhead |
E121467
|
entity |
| Predicate | mentionsTopic |
P831
|
FINISHED |
| Object | microblogging |
—
|
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: microblogging | Statement: [Evhead, mentionsTopic, microblogging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsTopic Context triple: [Evhead, mentionsTopic, microblogging]
-
A.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
C.
legacyTopic
Indicates that a topic or subject is considered outdated, superseded, or retained only for backward compatibility or historical reasons.
-
D.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
E.
featuresTopic
Indicates that something (such as a work, event, or item) prominently includes, focuses on, or is organized around a particular topic.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.