Triple
T16229282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtuosity |
E393935
|
entity |
| Predicate | hasArtificialIntelligenceCharacter |
P36900
|
FINISHED |
| Object | SID 6.7 |
—
|
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: SID 6.7 | Statement: [Virtuosity, hasArtificialIntelligenceCharacter, SID 6.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtificialIntelligenceCharacter Context triple: [Virtuosity, hasArtificialIntelligenceCharacter, SID 6.7]
-
A.
hasAI
Indicates that one entity possesses, incorporates, or is equipped with an artificial intelligence system.
-
B.
hasArtificialCrewmember
Indicates that an entity includes at least one crew member that is artificial (e.g., a robot or AI) rather than biological.
-
C.
aiCharacter
chosen
Indicates that an entity is a character or agent whose behavior or role is driven by artificial intelligence.
-
D.
hasRobotCharacterRole
Indicates that an entity participates in a role or function specifically as a robot character within a given context or work.
-
E.
hasAnimatronicCharacter
Indicates that an entity features, includes, or is associated with an animatronic character.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2889688190ac04e4e9479cabf4 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.