Triple
T27753399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Such a Long Journey |
E701271
|
entity |
| Predicate | mainCharacterCommunity |
P174355
|
FINISHED |
| Object | Parsi |
—
|
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: Parsi | Statement: [Such a Long Journey, mainCharacterCommunity, Parsi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterCommunity Context triple: [Such a Long Journey, mainCharacterCommunity, Parsi]
-
A.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
B.
exampleCharacter
Indicates that one entity is an illustrative or sample character associated with another entity, typically used for demonstration or example purposes.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
E.
hasLocalCommunityCharacter
Indicates that something possesses qualities or attributes typical of a specific local community or neighborhood.
- F. None of above. chosen
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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 27, 2026, 4:22 p.m.