Triple
T27756121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Bug |
E701336
|
entity |
| Predicate | firstDiscovered |
P3836
|
FINISHED |
| Object | 2000-05-04 |
—
|
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: 2000-05-04 | Statement: [Love Bug, firstDiscovered, 2000-05-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDiscovered Context triple: [Love Bug, firstDiscovered, 2000-05-04]
-
A.
discoveryDate
chosen
Indicates the date on which something was first discovered or identified.
-
B.
firstMajorDiscovery
Indicates that the object is the earliest significant discovery or breakthrough associated with the subject.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
firstAppearedOnGlobeBy
Indicates that an entity made its first appearance or was first featured on a globe created or authored by the specified source.
-
E.
ageWhenDiscovered
Indicates the age of an entity at the time it was first discovered.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: April 27, 2026, 4:23 p.m.