Triple
T2659145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romeo Montague |
E54683
|
entity |
| Predicate | timeOfWork |
P7950
|
FINISHED |
| Object | late 16th century (date of composition) |
—
|
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: late 16th century (date of composition) | Statement: [Romeo Montague, timeOfWork, late 16th century (date of composition)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfWork Context triple: [Romeo Montague, timeOfWork, late 16th century (date of composition)]
-
A.
workPeriod
chosen
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
workLength
Indicates the duration or length of time associated with a particular work or task.
-
C.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
D.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
E.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94dcaa48190aec625f68ce61a02 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.