Triple
T31127733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deșteaptă-te, române! |
E793404
|
entity |
| Predicate | hasVerseCountApprox |
P7673
|
FINISHED |
| Object | 4 official verses (more in original poem) |
—
|
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: 4 official verses (more in original poem) | Statement: [Deșteaptă-te, române!, hasVerseCountApprox, 4 official verses (more in original poem)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerseCountApprox Context triple: [Deșteaptă-te, române!, hasVerseCountApprox, 4 official verses (more in original poem)]
-
A.
hasVerseCount
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
B.
approximateNumberOfVerses
chosen
Indicates an estimated or approximate count of verses associated with an entity.
-
C.
approximateNumberOfPoems
Indicates an estimated or roughly calculated count of poems associated with an entity.
-
D.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
E.
hasVerseRange
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:05 p.m.