Triple
T5450151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come and Take It |
E122348
|
entity |
| Predicate | dateOfFirstUse |
P24583
|
FINISHED |
| Object | 1835 |
—
|
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: 1835 | Statement: [Come and Take It, dateOfFirstUse, 1835]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstUse Context triple: [Come and Take It, dateOfFirstUse, 1835]
-
A.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
B.
firstYearOfUse
chosen
Indicates the year in which something was first put into use or began being used.
-
C.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
D.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.