Triple
T35797483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restoration-era Paris |
E1034872
|
entity |
| Predicate | notableWriterActiveIn |
P10455
|
FINISHED |
| Object | Victor Hugo |
E41183
|
NE 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: Victor Hugo | Statement: [Restoration-era Paris, notableWriterActiveIn, Victor Hugo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWriterActiveIn Context triple: [Restoration-era Paris, notableWriterActiveIn, Victor Hugo]
-
A.
hasNotableWriter
chosen
Indicates that an entity is associated with a writer who is recognized as significant or distinguished in some notable way.
-
B.
workOfAuthorActiveIn
Indicates that a work is created by an author during a period when that author is actively producing or engaged in their creative or professional activities.
-
C.
notableWorkWrittenIn
Indicates that a notable work was written in a particular language, place, or time period.
-
D.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
E.
notableAuthorMember
Indicates that an entity is a notable or distinguished author who is a member of a particular group, organization, or collection.
- F. None of above.
Provenance (4 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389167e7908190b20c8161c8554d0a |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.