Triple
T29035031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eusebius |
E737833
|
entity |
| Predicate | hasAlterEgoCounterpart |
P86336
|
FINISHED |
| Object | Florestan |
—
|
NE NERFINISHED |
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: Florestan | Statement: [Eusebius, hasAlterEgoCounterpart, Florestan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlterEgoCounterpart Context triple: [Eusebius, hasAlterEgoCounterpart, Florestan]
-
A.
hasFictionalAlterEgoOf
chosen
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
hasCounterpartNickname
Indicates that one entity is used as an alternative or counterpart nickname for another entity.
-
C.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
hasCounterpartName
Indicates that an entity has an alternative or corresponding name used as its counterpart in another context, system, or representation.
-
E.
hasDoppelganger
Indicates that an entity has a counterpart or double that closely resembles it, often in appearance, behavior, or role.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 9:57 a.m.