Triple
T26210356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manasamangal |
E655470
|
entity |
| Predicate | hasVersionBy |
P24368
|
FINISHED |
| Object | Bipradas Pipilai |
—
|
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: Bipradas Pipilai | Statement: [Manasamangal, hasVersionBy, Bipradas Pipilai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersionBy Context triple: [Manasamangal, hasVersionBy, Bipradas Pipilai]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasCanonicalVersionBy
Indicates that one entity is the officially recognized or standard version of another entity, as established or authored by a specific source or agent.
-
C.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
hasNotableVersionBy
chosen
Indicates that an entity has a notable or distinguished version, edition, or variant created or produced by a specific agent.
-
E.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 8:52 p.m.