Triple
T25889721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek: Q-Squared |
E652294
|
entity |
| Predicate | connectsCharacters |
P76158
|
FINISHED |
| Object | Q and Trelane |
—
|
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: Q and Trelane | Statement: [Star Trek: Q-Squared, connectsCharacters, Q and Trelane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCharacters Context triple: [Star Trek: Q-Squared, connectsCharacters, Q and Trelane]
-
A.
connectsCharacter
Indicates that one character is linked or associated with another in some meaningful way.
-
B.
gắnVớiNhânVật
Indicates a relationship in which something is associated, connected, or tied to a particular character or person.
-
C.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
D.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
E.
associatedCharacters
chosen
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 22, 2026, 8:19 a.m.