Triple
T32870607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mawtini |
E840778
|
entity |
| Predicate | originallyWrittenAs |
P140396
|
FINISHED |
| Object | patriotic 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: patriotic poem | Statement: [Mawtini, originallyWrittenAs, patriotic poem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyWrittenAs Context triple: [Mawtini, originallyWrittenAs, patriotic poem]
-
A.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
B.
originallyProducedAs
chosen
Indicates that one entity was first created, released, or manufactured in the form of another specified entity or format.
-
C.
actuallyWrittenBy
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
isWrittenAs
Indicates that one entity is represented or expressed in written form as another entity (such as a specific spelling, notation, or symbol).
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:17 a.m.