Triple
T273200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dragon in My Garage |
E5682
|
entity |
| Predicate | illustratesConcept |
P463
|
FINISHED |
| Object | unfalsifiable claims |
—
|
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: unfalsifiable claims | Statement: [The Dragon in My Garage, illustratesConcept, unfalsifiable claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: illustratesConcept Context triple: [The Dragon in My Garage, illustratesConcept, unfalsifiable claims]
-
A.
demonstratedConcept
chosen
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
challengedConcept
Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
-
E.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dcf667c8190a7b8630fe67b9a90 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7345c4819086c21710864a1b42 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.