Triple
T3171842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What Do We Do? We Fly! |
E66368
|
entity |
| Predicate | hasPunctuationInTitle |
P19764
|
FINISHED |
| Object | question mark |
—
|
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: question mark | Statement: [What Do We Do? We Fly!, hasPunctuationInTitle, question mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPunctuationInTitle Context triple: [What Do We Do? We Fly!, hasPunctuationInTitle, question mark]
-
A.
titlePunctuation
chosen
Indicates that a title includes specific punctuation marks or follows a particular punctuation pattern.
-
B.
hasTitlePun
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
C.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
hasOrdinaryTitle
Indicates that an entity holds a standard, non-noble or non-honorific title associated with its role or position.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada66da23c81908f063b44b48b1e53 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.