Triple
T21059018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripidean corpus |
E518801
|
entity |
| Predicate | hasCanonicalNumberOfCompletePlays |
P34848
|
FINISHED |
| Object | around 18 to 19 |
—
|
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: around 18 to 19 | Statement: [Euripidean corpus, hasCanonicalNumberOfCompletePlays, around 18 to 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalNumberOfCompletePlays Context triple: [Euripidean corpus, hasCanonicalNumberOfCompletePlays, around 18 to 19]
-
A.
numberOfKnownPlays
chosen
Indicates the total count of plays that are known to be associated with a given entity (such as an author, theater, or period).
-
B.
numberOfPlays
Indicates the total count of times an item, such as a track or media asset, has been played.
-
C.
completeGames
Indicates that an entity has finished participating in or playing a game from start to end.
-
D.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
E.
isFinalPlayBy
Indicates that a particular play or move is the last one performed by a specified entity in a sequence or event.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd8236b481908eebfaeeb2aa63e6 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:37 p.m.