Triple
T34151388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Becky |
E876006
|
entity |
| Predicate | universeConnectionType |
P113102
|
FINISHED |
| Object | same fictional universe or storyline as Endora |
—
|
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: same fictional universe or storyline as Endora | Statement: [Becky, universeConnectionType, same fictional universe or storyline as Endora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeConnectionType Context triple: [Becky, universeConnectionType, same fictional universe or storyline as Endora]
-
A.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
B.
inUniverseConnection
chosen
Indicates a relationship where one entity exists, occurs, or is relevant within the fictional or conceptual universe defined by another entity.
-
C.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
D.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
E.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:54 a.m.