Triple
T21865362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupa Capitolina |
E539869
|
entity |
| Predicate | hasComponentDate |
P140477
|
FINISHED |
| Object | she-wolf possibly 5th century BC |
—
|
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: she-wolf possibly 5th century BC | Statement: [Lupa Capitolina, hasComponentDate, she-wolf possibly 5th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentDate Context triple: [Lupa Capitolina, hasComponentDate, she-wolf possibly 5th century BC]
-
A.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
B.
hasTimeComponent
chosen
Indicates that something includes, is associated with, or is characterized by a specific temporal aspect or time-related element.
-
C.
hasVariableDate
Indicates that the associated date is not fixed but can change or vary depending on conditions or context.
-
D.
hasDateContext
Indicates that something is associated with, constrained by, or interpreted within a specific date or time-related context.
-
E.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63e70c08190a9ba90c47c4060d4 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.