Triple
T32193849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Seer machine |
E822345
|
entity |
| Predicate | hasFanReplicas |
P16046
|
FINISHED |
| Object | coin-operated replicas |
—
|
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: coin-operated replicas | Statement: [Mystic Seer machine, hasFanReplicas, coin-operated replicas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFanReplicas Context triple: [Mystic Seer machine, hasFanReplicas, coin-operated replicas]
-
A.
hasReplicaDisplays
chosen
Indicates that an entity features or presents one or more replica items as displays.
-
B.
hasReplicators
Indicates that an entity possesses or is equipped with devices or mechanisms capable of reproducing or duplicating objects, structures, or materials.
-
C.
supportsDataReplicationFactor
Indicates that an entity enables, configures, or is compatible with a specified data replication factor for storing or duplicating data.
-
D.
hasReplicaStatus
Indicates that one entity serves as a copy or duplicate of another, often with a specific role or state in a replication relationship.
-
E.
replicaOf
Indicates that one entity is an exact or near-exact copy of another entity, preserving its form, structure, or content.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 12:35 a.m.